Ubuntu
ser package

Cannot create PID file at startup

Bug #633182 reported by Daniel Voina
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ser (Debian)
Fix Released
Unknown
ser (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ser

I have installed ser . I have checked that it worked and made a couple of test calls with it.
Then after a restart of the machine I have noticed that ser is not running and cannot be started.
I have added the logging to syslog in the ser.cfg file and I have had this output in /var/log/messages:

Sep 8 15:57:54 softswitch ser: init_tcp: using epoll_lt as the io watch method (auto detected)
Sep 8 15:57:54 softswitch ser: unable to create pid file /var/run/ser/ser.pid: No such file or directory
Sep 8 15:57:55 softswitch ser: init_tcp: using epoll_lt as the io watch method (auto detected)
Sep 8 15:57:55 softswitch ser: unable to create pid file /var/run/ser/ser.pid: No such file or directory
Sep 8 15:59:25 softswitch ser: init_tcp: using epoll_lt as the io watch method (auto detected)
Sep 8 15:59:25 softswitch ser: unable to create pid file /var/run/ser/ser.pid: No such file or directory
Sep 8 16:00:55 softswitch ser: init_tcp: using epoll_lt as the io watch method (auto detected)
Sep 8 16:00:55 softswitch ser: unable to create pid file /var/run/ser/ser.pid: No such file or directory

It seems that the directory /var/run/ser is deleted on system restart and hence the startup of ser is compromised as it wants to create its pid file in this directory.

Related branches

lp:ubuntu/maverick/ser
Revision history for this message
Daniel Voina (dvoina-deactivatedaccount) wrote :

Workaround for this:

edit as root the file /etc/init.d.ser and change the line

PIDFILE=/var/run/$NAME/$NAME.pid
into
PIDFILE=/var/run/$NAME.pid

Niall Creech (sevenmachines-deactivatedaccount)
Changed in ser (Ubuntu):
status: New → Confirmed
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

Added debian bug to see if it can be fixed there. adding an init script check should do this

tags: added: patch patch-forwarded-debian
Niall Creech (sevenmachines-deactivatedaccount)
Changed in ser (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → SevenMachines (sevenmachines)
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

Debdiff uploaded

test build: https://edge.launchpad.net/~sevenmachines/+archive/release+1/+packages

ser (2.0.0-4ubuntu1) maverick; urgency=low

  * debian/ser.init:
    - Check for /var/run/ser on startup and create if it doesnt exist,
    this is needed on systems where this directory is temporary (LP: #633182)

Changed in ser (Ubuntu):
status: In Progress → Confirmed
assignee: SevenMachines (sevenmachines) → nobody
Stefano Rivera (stefanor)
Changed in ser (Ubuntu):
importance: Undecided → Medium
Stefano Rivera (stefanor)
Changed in ser (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Stefano Rivera (stefanor) wrote :

Auto-closing bugs is still down...

openscap (0.5.8-1ubuntu1) maverick; urgency=low

  * debian/python-openscap.install: Change usr/lib/python*/site-packages
    line to usr/lib/python*/*-packages to fix FTBFS. (LP: #636883)

Changed in ser (Ubuntu):
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in ser (Debian):
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in ser (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.