Operating system name and version: Win2003 Standard SP2
Version of smsd: 3.1.8
Smsd installed from: sources
Name and model of a modem / phone: SIEMENS TC35
Interface: USB

I cannot know why the smsd always hang.
The folder checked have a LOCK file stuck in the directory.

2010-07-08 22:30:25,6, GSM1: Checking if modem is ready 2010-07-08 22:30:25,7, GSM1: -> AT 2010-07-08 22:30:25,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:25,7, GSM1: <- OK 2010-07-08 22:30:25,6, GSM1: Pre-initializing modem 2010-07-08 22:30:25,7, GSM1: -> ATE0+CMEE=1 2010-07-08 22:30:26,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:26,7, GSM1: <- OK 2010-07-08 22:30:26,7, GSM1: -> AT+CSQ 2010-07-08 22:30:26,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:27,7, GSM1: <- +CSQ: 10,99 OK 2010-07-08 22:30:27,6, GSM1: Signal Strength Indicator: (10,99) -93 dBm, Bit Error Rate: not known or not detectable 2010-07-08 22:30:27,6, GSM1: Checking if Modem is registered to the network 2010-07-08 22:30:27,7, GSM1: -> AT+CREG? 2010-07-08 22:30:27,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:28,7, GSM1: <- +CREG: 0,1 OK 2010-07-08 22:30:28,6, GSM1: Modem is registered to the network 2010-07-08 22:30:28,6, GSM1: Selecting PDU mode 2010-07-08 22:30:28,7, GSM1: -> AT+CMGF=0 2010-07-08 22:30:28,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:28,7, GSM1: <- OK 2010-07-08 22:30:28,6, GSM1: Checking memory size 2010-07-08 22:30:29,7, GSM1: -> AT+CPMS? 2010-07-08 22:30:29,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:29,7, GSM1: <- +CPMS: "SM",0,50,"SM",0,50,"SM",0,50 OK 2010-07-08 22:30:29,6, GSM1: Used memory is 0 of 50 2010-07-08 22:30:29,6, GSM1: No SMS received 2010-07-08 22:30:32,5, smsd: Moved file /var/spool/sms/smsout/2010_06_8_22_30_28_54321.txt to /var/spool/sms/checked 2010-07-08 22:30:33,6, GSM1: I have to send 1 short message for /var/spool/sms/checked/2010_06_8_22_30_28_54321.txt 2010-07-08 22:30:33,6, GSM1: Sending SMS from to xxxxxxx 2010-07-08 22:30:33,6, GSM1: Checking if modem is ready 2010-07-08 22:30:33,5, smsd: Moved file /var/spool/sms/smsout/2010_06_8_22_30_28_12231.txt to /var/spool/sms/checked 2010-07-08 22:30:33,7, GSM1: -> AT 2010-07-08 22:30:33,7, GSM1: Command is sent, waiting for the answer 2010-07-08 22:30:34,7, GSM1: <- OK 2010-07-08 22:30:34,6, GSM1: Pre-initializing modem 2010-07-08 22:30:34,7, GSM1: -> ATE0+CMEE=1 2010-07-08 22:30:34,7, GSM1: Command is sent, waiting for the answer

This is log of today. After the last line, all things stopped.
If I run "net stop smsd", the program cannot be terminated.
I need to kill the smsd.exe using task manager and run "net start smsd" then everything works fine.

Please advice what can I do to solve the problem. Thanks.

I do not know what causes this problem. In this post, michel has the similar problem on Windows XP with USB connection.

Perhaps you could try to re-install drivers, or even whole Cygwin. It seems that the driver freezes, and smsd cannot do anything because the read() function does not return.

I run a complete USB setup and have also had hangs. Most of my hangs were cured by setting pre-init to no and lowering the baudrate to 19,200.

I still hang on occasion but it is the result of the flakiness in XP handling usb. If for some reason my modems decide to detach and reattach, smsd will hang without warning until it tries to write to the modem (log lvl 5 that is).

Make sure you have good power -use a dual usb power cable if you have to or use a powered hub.

finnman wrote

I run a complete USB setup and have also had hangs. Most of my hangs were cured by setting pre-init to no and lowering the baudrate to 19,200.

Maybe this is a hint. Disabling pre-init should not have an effect, as it is just a command which is sent to the modem right after OK answer is received for AT command. But because it has impact, perhaps slower communication is required. There is a setting available for some problematic modems: communication_delay. It defines minimum time in milliseconds between latest answer from modem and next command which will be sent to modem. Perhaps some value 100, 250 or even 500 could be tried, if it helps.