[Serusers] Starting SER : PID file exists(/var/run/ser.pid)already running?
Aisling O'Driscoll
ashling.odriscoll at cit.ie
Tue Apr 12 12:30:18 CEST 2005
Ok I still have this error. However I have manageed to start SER
another way.
I did "find / -name ser_mysql.sh" beacuse I thought the problem
stemmed from my database. I then deleted all the ser_mysql.sh scripts
that werent supposed to exists out the /opt/ser directories. i did a
manual drop the database and then started the mysql script as
/opt/ser/sbin/ser_mysql.sh create. This worked and the tables are
updated e.g. verion is now table_version.
I still get an error when I start SER as /opt/ser/sbin/serctl start
(PID already exists). However the server works when i start it as ser
-d -E.
---- Original Message ----
From: ashling.odriscoll at cit.ie
To: ashling.odriscoll at cit.ie, greger at teigre.com,
ashling.odriscoll at cit.ie
Subject: Re: [Serusers] Starting SER : PID file
exists(/var/run/ser.pid)already running?
Date: Mon, 11 Apr 2005 17:26:11 +0100
>By the way I have tried dropping the tbale manually: mysqladmin -u
>root -p <password> drop ser
>then /opt/ser/sbin/ser_mysql.sh create.
>
>>
>>---- Original Message ----
>>From: ashling.odriscoll at cit.ie
>>To: greger at teigre.com, ashling.odriscoll at cit.ie
>>Subject: Re: [Serusers] Starting SER : PID file
>>exists(/var/run/ser.pid)already running?
>>Date: Mon, 11 Apr 2005 17:17:44 +0100
>>
>>>Hi Greger,
>>>
>>>The error seems to be ERROR: : fix_expr : fix_actions error
>>>
>>>I reckon this is something got to do with mysql database because I
>>>dont think it updated. However when I do /opt/ser/sbin/ser_mysql.sh
>>>drop and /opt/ser/sbin/ser_mysql.sh, the database still isnt
>updated
>>>i.e. it has a column "version" instead of "table_version" in the
>>>version table of the SER database. What can I do??
>>>
>>>localhost:~ # /opt/ser/sbin/ser -D -E
>>>Listening on
>>> udp: 127.0.0.1 [127.0.0.1]:5060
>>> udp: 157.190.74.152 [157.190.74.152]:5060
>>> tcp: 127.0.0.1 [127.0.0.1]:5060
>>> tcp: 157.190.74.152 [157.190.74.152]:5060
>>>Aliases:
>>> tcp: localhost.localdomain:5060
>>> tcp: localhost:5060
>>> udp: localhost.localdomain:5060
>>> udp: localhost:5060
>>> *: 157.190.74.152:5060:*
>>>
>>>WARNING: no fork mode and more than one listen address found(will
>>>use only the the first one)
>>>stateless - initializing
>>> 0(0) Maxfwd module- initializing
>>>textops - initializing
>>> 0(0) db_url=(nil)
>>> 0(0) db_url=
>>> 0(0) db_url.len=0
>>> 0(0) pa_domain=sip.handhelds.org
>>> 0(0) pa_mod: use_db=0 db_url.s= pa_domain=sip.handhelds.org
>>> 0(0) pa_mod_init done
>>> 0(0) submit_query(): Unknown column 'table_version' in 'field
>list'
>>> 0(0) submit_query(): Error while submitting query
>>> 0(0) table_version(): Error in db_query
>>> 0(0) register_udomain(): Error while querying table version
>>> 0(0) domain_fixup(): Error while registering domain
>>> 0(0) ERROR: fix_expr : fix_actions error
>>>ERROR: error -1 while trying to fix configuration
>>>localhost:~ # /opt/ser/sbin/ser -c
>>>Listening on
>>> udp: 127.0.0.1 [127.0.0.1]:5060
>>> udp: 157.190.74.152 [157.190.74.152]:5060
>>> tcp: 127.0.0.1 [127.0.0.1]:5060
>>> tcp: 157.190.74.152 [157.190.74.152]:5060
>>>Aliases:
>>> tcp: localhost.localdomain:5060
>>> tcp: localhost:5060
>>> udp: localhost.localdomain:5060
>>> udp: localhost:5060
>>> *: 157.190.74.152:5060:*
>>>
>>>config file ok, exiting...
>>>>
>>>>---- Original Message ----
>>>>From: greger at teigre.com
>>>>To: ashling.odriscoll at cit.ie
>>>>Subject: Re: [Serusers] Starting SER : PID file
>>>>exists(/var/run/ser.pid)already running?
>>>>Date: Sun, 10 Apr 2005 11:39:19 +0200
>>>>
>>>>>Seems like the output from the end of SER's exit. Could you post
>>the
>>>>whole
>>>>>output? Somewhere you should have an error...
>>>>>g-)
>>>>>
>>>>>Aisling O'Driscoll wrote:
>>>>>> Hello,
>>>>>>
>>>>>> If I start SER with "ser -d -d -d -d -d -d -d -D -E". I get
>>>>something
>>>>>> like the following:
>>>>>>
>>>>>> 0(0) qm_free(0x8109b00, 0x8145548), called from script_cb.c:
>>>>>> destroy_script_cb(81)
>>>>>> 0(0) qm_free: freeing frag. 0x8145530 alloc'ed from
>script_cb.c:
>>>>>> register_script_cb(53)
>>>>>> 0(0) qm_free(0x8109b00, 0x8145850), called from script_cb.c:
>>>>>> destroy_script_cb(83)
>>>>>> 0(0) qm_free: freeing frag. 0x8145838 alloc'ed from
>script_cb.c:
>>>>>> register_script_cb(53)
>>>>>> 0(0) qm_free(0x4045b000, 0x4049153c), called from main.c:
>>>>>> cleanup(373)
>>>>>> 0(0) qm_free: freeing frag. 0x40491524 alloc'ed from main.c:
>>>>>> main(1534)
>>>>>> 0(13787) shm_mem_destroy
>>>>>> 0(13787) destroying the shared memory lock
>>>>>> localhost:/opt/ser/sbin # pstree
>>>>>>
>>>>>> ....Does that explain anything? Again when I do pstree, I see
>2*
>>>>>> [ser] instead of the usual 27 *[ser].
>>>>>>
>>>>>> Kindest regards,
>>>>>> Aisling
>>>>>>>
>>>>>>> ---- Original Message ----
>>>>>>> From: greger at teigre.com
>>>>>>> To: ashling.odriscoll at cit.ie, llanosserna at hotmail.com
>>>>>>> Subject: Re: [Serusers] Starting SER : PID file
>>>>>>> exists(/var/run/ser.pid)already running?
>>>>>>> Date: Fri, 8 Apr 2005 19:30:22 +0200
>>>>>>>
>>>>>>>> Try to start ser up in debug/no-fork mode!! You will see if
>>it
>>>>>>> crashes.
>>>>>>>> g-)
>>>>>>>>
>>>>>>>> Aisling O'Driscoll wrote:
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> When I removed the ser.pid file from /var/run and ran
>>>>>>>>> /opt/ser/sbin/serctl start, it said SER had started. Then
>>when
>>>>I
>>>>>>> look
>>>>>>>>> at pstree, I see 2 * [ser]. However usually when SER is
>>working
>>>>>>>>> properly it says 27 * [ser]. When I check netstat -tunap, I
>>>>dont
>>>>>>> see
>>>>>>>>> SER working.
>>>>>>>>>
>>>>>>>>> Any other ideas?
>>>>>>>>>
>>>>>>>>> ---- Original Message ----
>>>>>>>>> From: llanosserna at hotmail.com
>>>>>>>>> To: ashling.odriscoll at cit.ie
>>>>>>>>> Subject: RE: [Serusers] Starting SER : PID file exists
>>>>>>>>> (/var/run/ser.pid)already running?
>>>>>>>>> Date: Fri, 08 Apr 2005 13:53:25 +0200
>>>>>>>>>
>>>>>>>>>> <html><div style='background-color:'><DIV class=RTE></DIV>
>>>>>>>>>> <P>Make sure ser is not running with a </P>
>>>>>>>>>> <P>>ps -ef</P>
>>>>>>>>>> <P>I fit's not there, just remove the pid file</P>
>>>>>>>>>> <P>>rm /var/run/ser.pid</P>
>>>>>>>>>> <P>And then you should be able to start ser</P>
>>>>>>>>>> <P> </P>
>>>>>>>>>> <P> </P>
>>>>>>>>>> <P> </P>
>>>>>>>>>> <DIV class=RTE>>Hi, </DIV>
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>I am wondering if anyone has ever come
>across
>>>>this
>>>>>>>>>> error before?:
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>Starting SER : PID file exists!
>>>>(/var/run/ser.pid)
>>>>>>>>>> already running?
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>I am using ser 0.9.0 and it worked like a
>>charm
>>>>>>> the
>>>>>>>>>> first few times
>>>>>>>>>> <DIV></DIV>>that I stopped and started SER. There are no
>>>>>>> errors in
>>>>>>>>>> <DIV></DIV>>/var/log/messages. I also started SER as
>>>>>>>>>> /opt/ser/sbin/ser -c and it
>>>>>>>>>> <DIV></DIV>>showed that the config was ok and exited.
>>>>However
>>>>>>> when
>>>>>>>>>> I check
>>>>>>>>>> <DIV></DIV>>pstree, I dont see SER listening.
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>Could it perhaps be something got to do with
>>>>the
>>>>>>>>>> database?. Example:
>>>>>>>>>> <DIV></DIV>>Should the version table in the SER database
>>>>>>> contain
>>>>>>>>>> "version" or
>>>>>>>>>> <DIV></DIV>>"table_version"? I have tried dropping and
>>>>>>> restarting
>>>>>>>>>> the database
>>>>>>>>>> <DIV></DIV>>i.e. /opt/ser/sbin/ser_mysql.sh drop, then
>>>>>>>>>> <DIV></DIV>>./opt/ser/sbin/ser_mysql.sh create.
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>Any ideas would be appreciated.
>>>>>>>>>> <DIV></DIV>>Thanks,
>>>>>>>>>> <DIV></DIV>>Aisling.
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>>
>>>>>>>
>>>><DIV></DIV>>-------------------Legal Disclaimer-----
>-
>>--
>>>>>>>>>> -------------------------------
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>> <DIV></DIV>>The above electronic mail transmission is
>>>>>>> confidential
>>>>>>>>>> and intended only for the person to whom it is addressed.
>>Its
>>>>>>>>>> contents may be protected by legal and/or professional
>>>>privilege.
>>>>>>>>>> Should it be received by you in error please contact the
>>>>sender
>>>>>>> at
>>>>>>>>>> the above quoted email address. Any unauthorised form of
>>>>>>> reproduction
>>>>>>>>>> of this message is strictly prohibited. The Institute does
>>not
>>>>>>>>>> guarantee the security of any information electronically
>>>>>>> transmitted
>>>>>>>>>> and is not liable if the information contained in this
>>>>>>> communication
>>>>>>>>>> is not a proper and complete record of the message as
>>>>transmitted
>>>>>>> by
>>>>>>>>>> the sender nor for any delay in its receipt.
>>>>>>>>>> <DIV></DIV>>
>>>>>>>>>>
>><DIV></DIV>>_______________________________________________
>>>>>>>>>> <DIV></DIV>>Serusers mailing list
>>>>>>>>>> <DIV></DIV>>Serusers at iptel.org
>>>>>>>>>>
>><DIV></DIV>>http://mail.iptel.org/mailman/listinfo/serusers
>>>>>>>>>> <DIV></DIV></div></html>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -------------------Legal
>>>>>>>>>> Disclaimer---------------------------------------
>>>>>>>>>>
>>>>>>>>>> The above electronic mail transmission is confidential and
>>>>>>> intended
>>>>>>>>>> only for the person to whom it is addressed. Its contents
>>may
>>>>be
>>>>>>>>>> protected by legal and/or professional privilege. Should it
>>be
>>>>>>>>>> received by you in error please contact the sender at the
>>>>above
>>>>>>>>>> quoted email address. Any unauthorised form of reproduction
>>of
>>>>>>> this
>>>>>>>>>> message is strictly prohibited. The Institute does not
>>>>guarantee
>>>>>>> the
>>>>>>>>>> security of any information electronically transmitted and
>>is
>>>>not
>>>>>>>>>> liable if the information contained in this communication
>is
>>>>not
>>>>>>> a
>>>>>>>>>> proper and complete record of the message as transmitted by
>>>>the
>>>>>>>>>> sender nor for any delay in its receipt.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -------------------Legal
>>>>>>>>> Disclaimer---------------------------------------
>>>>>>>>>
>>>>>>>>> The above electronic mail transmission is confidential and
>>>>>>> intended
>>>>>>>>> only for the person to whom it is addressed. Its contents
>may
>>>>be
>>>>>>>>> protected by legal and/or professional privilege. Should it
>>be
>>>>>>>>> received by you in error please contact the sender at the
>>above
>>>>>>>>> quoted email address. Any unauthorised form of reproduction
>>of
>>>>>>> this
>>>>>>>>> message is strictly prohibited. The Institute does not
>>>>guarantee
>>>>>>> the
>>>>>>>>> security of any information electronically transmitted and
>is
>>>>not
>>>>>>>>> liable if the information contained in this communication is
>>>>not a
>>>>>>>>> proper and complete record of the message as transmitted by
>>the
>>>>>>>>> sender nor for any delay in its receipt.
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Serusers mailing list
>>>>>>>>> Serusers at iptel.org
>>>>>>>>> http://mail.iptel.org/mailman/listinfo/serusers
>>>>>>>>
>>>>>>>> -------------------Legal
>>>>>>> Disclaimer---------------------------------------
>>>>>>>>
>>>>>>>> The above electronic mail transmission is confidential and
>>>>intended
>>>>>>> only for the person to whom it is addressed. Its contents may
>>be
>>>>>>> protected by legal and/or professional privilege. Should it be
>>>>>>> received by you in error please contact the sender at the
>above
>>>>>>> quoted email address. Any unauthorised form of reproduction of
>>>>this
>>>>>>> message is strictly prohibited. The Institute does not
>>guarantee
>>>>the
>>>>>>> security of any information electronically transmitted and is
>>not
>>>>>>> liable if the information contained in this communication is
>>not
>>>>a
>>>>>>> proper and complete record of the message as transmitted by
>the
>>>>>>> sender nor for any delay in its receipt.
>>>>>>
>>>>>>
>>>>>> -------------------Legal
>>>>>> Disclaimer---------------------------------------
>>>>>>
>>>>>> The above electronic mail transmission is confidential and
>>>>intended
>>>>>> only for the person to whom it is addressed. Its contents may
>be
>>>>>> protected by legal and/or professional privilege. Should it be
>>>>>> received by you in error please contact the sender at the above
>>>>>> quoted email address. Any unauthorised form of reproduction of
>>>>this
>>>>>> message is strictly prohibited. The Institute does not
>guarantee
>>>>the
>>>>>> security of any information electronically transmitted and is
>>not
>>>>>> liable if the information contained in this communication is
>not
>>a
>>>>>> proper and complete record of the message as transmitted by the
>>>>>> sender nor for any delay in its receipt.
>>>>>
>>>>>
>>>>>-------------------Legal
>>>>Disclaimer---------------------------------------
>>>>>
>>>>>The above electronic mail transmission is confidential and
>>intended
>>>>only for the person to whom it is addressed. Its contents may be
>>>>protected by legal and/or professional privilege. Should it be
>>>>received by you in error please contact the sender at the above
>>>>quoted email address. Any unauthorised form of reproduction of
>this
>>>>message is strictly prohibited. The Institute does not guarantee
>>the
>>>>security of any information electronically transmitted and is not
>>>>liable if the information contained in this communication is not a
>>>>proper and complete record of the message as transmitted by the
>>>>sender nor for any delay in its receipt.
>
>
>-------------------Legal
>Disclaimer---------------------------------------
>
>The above electronic mail transmission is confidential and intended
>only for the person to whom it is addressed. Its contents may be
>protected by legal and/or professional privilege. Should it be
>received by you in error please contact the sender at the above
>quoted email address. Any unauthorised form of reproduction of this
>message is strictly prohibited. The Institute does not guarantee the
>security of any information electronically transmitted and is not
>liable if the information contained in this communication is not a
>proper and complete record of the message as transmitted by the
>sender nor for any delay in its receipt.
>
-------------------Legal Disclaimer---------------------------------------
The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.
More information about the sr-users
mailing list