Scripting Start/Stop

[Jeep Hauser]

Hi Folks,

I'm seeing some oddity with my (server version 8.5.0) stop/backup/start
script. It appears that S99mmserverX stop' doesn't kill onmuxd
(apparently it cannot find it), because when I try to restart, I get
this message:

Stopping Meeting Maker Server
ServerLaunch - Success: Meeting Maker Server process ended.
ServerLaunch - WARNING: Could not locate Meeting Maker Onmux Process.
Backing Up Meeting Maker Server Data
Starting Meeting Maker Server
ServerLaunch - Success: Meeting Maker Onmux process started.
ServerLaunch - Success: Meeting Maker Server process started.
Meeting Maker (TM) Server. Version 8.5
(c) 2004, Meeting Maker, Inc.

ServerLaunch - Success: Meeting Maker Server process started.
host:/etc/periodic/daily administrator$ onmuxd: error binding socket to
tcp mux port 417; status = 1660; This may be caused either by onmuxd not
being run with privileges or that onmuxd is already running.

onmuxd: error binding socket to tcp mux port 417; status = 1660; This
may be caused either by onmuxd not being run with privileges or that
onmuxd is already running.

However, the server does restart and functions properly (or so it seems).

Any tips? I've included the full script below.

Jeep


#!/bin/sh
MMSERVERHOME="/Library/meetingmaker/server"
MMSERVERSUBDIR="/Library/meetingmaker/data/MyServerName"
DATESTAMP=`date +%m%d%y`
#
# stop the meetingmaker process
#
echo "Stopping Meeting Maker Server"
/Library/meetingmaker/server/S99mmserverX stop
#
# backup the meetingmaker server data
#
echo "Backing Up Meeting Maker Server Data"
cp "$MMSERVERSUBDIR/MMDATA.mdb" "$MMSERVERSUBDIR/$DATESTAMP.MMDATA.BAK"
#
# start the server
#
echo "Starting Meeting Maker Server"
/Library/meetingmaker/server/S99mmserverX -c
/Library/meetingmaker/server/serverconf.txt start
exit 0


--
Jeep Hauser
Director
IT & Communications

University of Southern California
Career Planning & Placement Center
<mailto:***@usc.edu>
<http://careers.usc.edu>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Aaron Levitt]

Hi Jeep-

We encountered the same thing with our scripts. It seems that the
new binaries(?) seem to call onmuxd. So, the first time you run the
script, it (attempts) to do the correct thing, which is start onmuxd,
and then the server. However, it's not smart enough to realize that
onmuxd is already running, so it tries again. We currently have a
bug open with them that still hasn't been resolved. Bug ID # 13836.

Hope that helps!

-=Aaron

On Oct 21, 2005, at 9:25 AM, Jeep Hauser wrote:

> Hi Folks,
>
> I'm seeing some oddity with my (server version 8.5.0) stop/backup/
> start script. It appears that S99mmserverX stop' doesn't kill
> onmuxd (apparently it cannot find it), because when I try to
> restart, I get this message:
>
> Stopping Meeting Maker Server
> ServerLaunch - Success: Meeting Maker Server process ended.
> ServerLaunch - WARNING: Could not locate Meeting Maker Onmux Process.
> Backing Up Meeting Maker Server Data
> Starting Meeting Maker Server
> ServerLaunch - Success: Meeting Maker Onmux process started.
> ServerLaunch - Success: Meeting Maker Server process started.
> Meeting Maker (TM) Server. Version 8.5
> (c) 2004, Meeting Maker, Inc.
>
> ServerLaunch - Success: Meeting Maker Server process started.
> host:/etc/periodic/daily administrator$ onmuxd: error binding
> socket to tcp mux port 417; status = 1660; This may be caused
> either by onmuxd not being run with privileges or that onmuxd is
> already running.
>
> onmuxd: error binding socket to tcp mux port 417; status = 1660;
> This may be caused either by onmuxd not being run with privileges
> or that onmuxd is already running.
>
> However, the server does restart and functions properly (or so it
> seems).
>
> Any tips? I've included the full script below.
>
> Jeep
>
>
> #!/bin/sh
> MMSERVERHOME="/Library/meetingmaker/server"
> MMSERVERSUBDIR="/Library/meetingmaker/data/MyServerName"
> DATESTAMP=`date +%m%d%y`
> #
> # stop the meetingmaker process
> #
> echo "Stopping Meeting Maker Server"
> /Library/meetingmaker/server/S99mmserverX stop
> #
> # backup the meetingmaker server data
> #
> echo "Backing Up Meeting Maker Server Data"
> cp "$MMSERVERSUBDIR/MMDATA.mdb" "$MMSERVERSUBDIR/
> $DATESTAMP.MMDATA.BAK"
> #
> # start the server
> #
> echo "Starting Meeting Maker Server"
> /Library/meetingmaker/server/S99mmserverX -c /Library/meetingmaker/
> server/serverconf.txt start
> exit 0
>
>
> --
> Jeep Hauser
> Director
> IT & Communications
>
> University of Southern California
> Career Planning & Placement Center
> <mailto:***@usc.edu>
> <http://careers.usc.edu>
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Jeep Hauser]

Hi Aaron,

Well, good to know I'm not alone. ;-) Your bug isn't in the public list
of bugs, but good to know about it. I submitted a feature request to at
least write a pid to /var/run.

Thanks,
Jeep


on 10/21/05 1:54 PM Aaron Levitt wrote:
> Hi Jeep-
>
> We encountered the same thing with our scripts. It seems that the new
> binaries(?) seem to call onmuxd. So, the first time you run the
> script, it (attempts) to do the correct thing, which is start onmuxd,
> and then the server. However, it's not smart enough to realize that
> onmuxd is already running, so it tries again. We currently have a bug
> open with them that still hasn't been resolved. Bug ID # 13836.
>
> Hope that helps!
>
> -=Aaron
>
> On Oct 21, 2005, at 9:25 AM, Jeep Hauser wrote:
>
>> Hi Folks,
>>
>> I'm seeing some oddity with my (server version 8.5.0) stop/backup/
>> start script. It appears that S99mmserverX stop' doesn't kill onmuxd
>> (apparently it cannot find it), because when I try to restart, I get
>> this message:
>>
>> Stopping Meeting Maker Server
>> ServerLaunch - Success: Meeting Maker Server process ended.
>> ServerLaunch - WARNING: Could not locate Meeting Maker Onmux Process.
>> Backing Up Meeting Maker Server Data
>> Starting Meeting Maker Server
>> ServerLaunch - Success: Meeting Maker Onmux process started.
>> ServerLaunch - Success: Meeting Maker Server process started.
>> Meeting Maker (TM) Server. Version 8.5
>> (c) 2004, Meeting Maker, Inc.
>>
>> ServerLaunch - Success: Meeting Maker Server process started.
>> host:/etc/periodic/daily administrator$ onmuxd: error binding socket
>> to tcp mux port 417; status = 1660; This may be caused either by
>> onmuxd not being run with privileges or that onmuxd is already running.
>>
>> onmuxd: error binding socket to tcp mux port 417; status = 1660; This
>> may be caused either by onmuxd not being run with privileges or that
>> onmuxd is already running.
>>
>> However, the server does restart and functions properly (or so it
>> seems).
>>
>> Any tips? I've included the full script below.
>>
>> Jeep
>>
>>
>> #!/bin/sh
>> MMSERVERHOME="/Library/meetingmaker/server"
>> MMSERVERSUBDIR="/Library/meetingmaker/data/MyServerName"
>> DATESTAMP=`date +%m%d%y`
>> #
>> # stop the meetingmaker process
>> #
>> echo "Stopping Meeting Maker Server"
>> /Library/meetingmaker/server/S99mmserverX stop
>> #
>> # backup the meetingmaker server data
>> #
>> echo "Backing Up Meeting Maker Server Data"
>> cp "$MMSERVERSUBDIR/MMDATA.mdb" "$MMSERVERSUBDIR/ $DATESTAMP.MMDATA.BAK"
>> #
>> # start the server
>> #
>> echo "Starting Meeting Maker Server"
>> /Library/meetingmaker/server/S99mmserverX -c /Library/meetingmaker/
>> server/serverconf.txt start
>> exit 0
>>
>>
>> --
>> Jeep Hauser
>> Director
>> IT & Communications
>>
>> University of Southern California
>> Career Planning & Placement Center
>> <mailto:***@usc.edu>
>> <http://careers.usc.edu>
>>
>>
>> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
>> TALK.HTML
>
>
>

--
Jeep Hauser
Director
IT & Communications

University of Southern California
Career Planning & Placement Center
<mailto:***@usc.edu>
<http://careers.usc.edu>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Joseph Hargitai]

you are not alone -

--
Joseph Hargitai
ITS eServices

On Fri, 21 Oct 2005, Jeep Hauser wrote:

> Hi Aaron,
>
> Well, good to know I'm not alone. ;-) Your bug isn't in the public list
> of bugs, but good to know about it. I submitted a feature request to at
> least write a pid to /var/run.
>
> Thanks,
> Jeep
>
>
> on 10/21/05 1:54 PM Aaron Levitt wrote:
> > Hi Jeep-
> >
> > We encountered the same thing with our scripts. It seems that the new
> > binaries(?) seem to call onmuxd. So, the first time you run the
> > script, it (attempts) to do the correct thing, which is start onmuxd,
> > and then the server. However, it's not smart enough to realize that
> > onmuxd is already running, so it tries again. We currently have a bug
> > open with them that still hasn't been resolved. Bug ID # 13836.
> >
> > Hope that helps!
> >
> > -=Aaron
> >
> > On Oct 21, 2005, at 9:25 AM, Jeep Hauser wrote:
> >
> >> Hi Folks,
> >>
> >> I'm seeing some oddity with my (server version 8.5.0) stop/backup/
> >> start script. It appears that S99mmserverX stop' doesn't kill onmuxd
> >> (apparently it cannot find it), because when I try to restart, I get
> >> this message:
> >>
> >> Stopping Meeting Maker Server
> >> ServerLaunch - Success: Meeting Maker Server process ended.
> >> ServerLaunch - WARNING: Could not locate Meeting Maker Onmux Process.
> >> Backing Up Meeting Maker Server Data
> >> Starting Meeting Maker Server
> >> ServerLaunch - Success: Meeting Maker Onmux process started.
> >> ServerLaunch - Success: Meeting Maker Server process started.
> >> Meeting Maker (TM) Server. Version 8.5
> >> (c) 2004, Meeting Maker, Inc.
> >>
> >> ServerLaunch - Success: Meeting Maker Server process started.
> >> host:/etc/periodic/daily administrator$ onmuxd: error binding socket
> >> to tcp mux port 417; status = 1660; This may be caused either by
> >> onmuxd not being run with privileges or that onmuxd is already running.
> >>
> >> onmuxd: error binding socket to tcp mux port 417; status = 1660; This
> >> may be caused either by onmuxd not being run with privileges or that
> >> onmuxd is already running.
> >>
> >> However, the server does restart and functions properly (or so it
> >> seems).
> >>
> >> Any tips? I've included the full script below.
> >>
> >> Jeep
> >>
> >>
> >> #!/bin/sh
> >> MMSERVERHOME="/Library/meetingmaker/server"
> >> MMSERVERSUBDIR="/Library/meetingmaker/data/MyServerName"
> >> DATESTAMP=`date +%m%d%y`
> >> #
> >> # stop the meetingmaker process
> >> #
> >> echo "Stopping Meeting Maker Server"
> >> /Library/meetingmaker/server/S99mmserverX stop
> >> #
> >> # backup the meetingmaker server data
> >> #
> >> echo "Backing Up Meeting Maker Server Data"
> >> cp "$MMSERVERSUBDIR/MMDATA.mdb" "$MMSERVERSUBDIR/ $DATESTAMP.MMDATA.BAK"
> >> #
> >> # start the server
> >> #
> >> echo "Starting Meeting Maker Server"
> >> /Library/meetingmaker/server/S99mmserverX -c /Library/meetingmaker/
> >> server/serverconf.txt start
> >> exit 0
> >>
> >>
> >> --
> >> Jeep Hauser
> >> Director
> >> IT & Communications
> >>
> >> University of Southern California
> >> Career Planning & Placement Center
> >> <mailto:***@usc.edu>
> >> <http://careers.usc.edu>
> >>
> >>
> >> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> >> TALK.HTML
> >
> >
> >
>
> --
> Jeep Hauser
> Director
> IT & Communications
>
> University of Southern California
> Career Planning & Placement Center
> <mailto:***@usc.edu>
> <http://careers.usc.edu>
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML