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(a)teigre.com > To: ashling.odriscoll(a)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(a)teigre.com >>>> To: ashling.odriscoll(a)cit.ie, llanosserna(a)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

> I >>>> look >>>>>> at pstree, I see 2 * [ser]. However usually when SER is

>>>>>> properly it says 27 * [ser]. When I check netstat -tunap, I >>>>>> dont see SER working. >>>>>> >>>>>> Any other ideas? >>>>>> >>>>>> ---- Original Message ---- >>>>>> From: llanosserna(a)hotmail.com >>>>>> To: ashling.odriscoll(a)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>&gt;ps -ef</P> >>>>>>> <P>I fit's not there, just remove the pid file</P> >>>>>>> <P>&gt;rm /var/run/ser.pid</P> >>>>>>> <P>And then you should be able to start ser</P> >>>>>>> <P>&nbsp;</P> >>>>>>> <P>&nbsp;</P> >>>>>>> <P>&nbsp;</P> >>>>>>> <DIV class=RTE>&gt;Hi, </DIV> >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt;I am wondering if anyone has ever come across > this >>>>>>> error before?: >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt;Starting SER : PID file exists! > (/var/run/ser.pid) >>>>>>> already running? >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt;I am using ser 0.9.0 and it worked like a >>>>>>> charm the first few times >>>>>>> <DIV></DIV>&gt;that I stopped and started SER. There are no >>>> errors in >>>>>>> <DIV></DIV>&gt;/var/log/messages. I also started SER as >>>>>>> /opt/ser/sbin/ser -c and it >>>>>>> <DIV></DIV>&gt;showed that the config was ok and exited. >>>>>>> However when I check >>>>>>> <DIV></DIV>&gt;pstree, I dont see SER listening. >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt;Could it perhaps be something got to do with > the >>>>>>> database?. Example: >>>>>>> <DIV></DIV>&gt;Should the version table in the SER database >>>> contain >>>>>>> "version" or >>>>>>> <DIV></DIV>&gt;"table_version"? I have tried dropping and >>>> restarting >>>>>>> the database >>>>>>> <DIV></DIV>&gt;i.e. /opt/ser/sbin/ser_mysql.sh drop, then >>>>>>> <DIV></DIV>&gt;./opt/ser/sbin/ser_mysql.sh create. >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt;Any ideas would be appreciated. >>>>>>> <DIV></DIV>&gt;Thanks, >>>>>>> <DIV></DIV>&gt;Aisling. >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt; >>>>>>> >>>> > <DIV></DIV>&gt;-------------------Legal&nbsp;&nbsp;Disclaimer------

>>>>>>> ------------------------------- >>>>>>> <DIV></DIV>&gt; >>>>>>> <DIV></DIV>&gt;The above electronic mail transmission is >>>> confidential >>>>>>> and intended only for the person to whom it is addressed.

>>>>>>> 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

>>>>>>> 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>&gt; >>>>>>>

>>>>>>> <DIV></DIV>&gt;Serusers mailing list >>>>>>> &lt;DIV&gt;&lt;/DIV&gt;&amp;gt;serusers(a)lists.iptel.org >>>>>>>

>>>>>>> <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

> 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

>>>>>> received by you in error please contact the sender at the

>>>>>> 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

>>>>>> sender nor for any delay in its receipt. >>>>>> >>>>>> _______________________________________________ >>>>>> Serusers mailing list >>>>>> serusers(a)lists.iptel.org >>>>>> http://lists.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

>>>> 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

>>>> 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

>>> liable if the information contained in this communication is not

>>> 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

> 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