I have noticed that sometimes on a production memcached service the restart command is not always reliable. If the memcached process has allocated a lot of memory, it sometimes take a little while to shut down.
The init.d script seems to approach this by inserting a "sleep 1" between the stop and start operations, but that's not always enough.
When the memcached service is started again it will fail to start with the error "failed to listen on TCP port XXXXX: Address already in use" since the dying process still owns the port.
Binary package hint: memcached
I have noticed that sometimes on a production memcached service the restart command is not always reliable. If the memcached process has allocated a lot of memory, it sometimes take a little while to shut down.
The init.d script seems to approach this by inserting a "sleep 1" between the stop and start operations, but that's not always enough.
When the memcached service is started again it will fail to start with the error "failed to listen on TCP port XXXXX: Address already in use" since the dying process still owns the port.
Release: Ubuntu 10.10
memcached: us-east- 1.ec2.archive. ubuntu. com/ubuntu/ maverick/main amd64 Packages dpkg/status
Installed: 1.4.5-1ubuntu1
Candidate: 1.4.5-1ubuntu1
Version table:
*** 1.4.5-1ubuntu1 0
500 http://
100 /var/lib/