| Keywords: Mode: All keywords (AND) |
|
Tue Mar 02, 2010 20:30
|
bb400: For some reason I assumed it was going through syslog... it's not a problem using another file for output.
Thanks
|
|
Tue Mar 02, 2010 20:23
|
bb400: Thanks Keke, but not needed for me - the modem regular_run is ideal since if the modem handler fails then it stops picking up messages from 'shared' and moving them to 'outgoing'.
I am, however, building a list of other suggestions :)
|
|
Tue Mar 02, 2010 16:05
|
bb400: Operating system name and version: Ubuntu 9.10
Version of smsd: 3.1.6
Smsd installed from: sources
Name and model of a modem / phone:
Interface:
I want my regular_run to output to the smsd log - for example I want to record the network status, and the total msg recorded every hour, like stats, but also record the output of eventscheduler scripts.
Do I have to muck around with logger or is there a simpler way?
thanks,
|
|
Tue Mar 02, 2010 11:47
|
bb400: In the global part of smsd.conf, define regular_run = /usr/local/bin/smsd_regular_run.sh and regular_run_interval = 10. Also define outgoing = /var/spool/sms/processdir and create this directory.
I ended up with a compromise - the regular run for the modem can mv every 30 seconds, whilst the global regular run I keep for reporting whether smd is active every 10 mins or so...
|
|
Sat Feb 27, 2010 20:06
|
bb400: Yes, that's a good idea, although I like the 'neatness' of using eventscheduler to get the *next* message - ie after every successful send, mv another message into outgoing and let smsd pick that one up.
The same problem exists though - how to kickstart the first mv - and regular_run would do that, but would it still do it if the modem was broken? I'm not sure if I want to use regular_run to say 'smsd is still working' if the modems are faulty or not.
I kind of think there is a mixed solution hidden here somewhere - if outgoing is empty then regular_run checks 'shared' and mv a single msg, and eventscheduler does the same.
As my other posting, it's all about what happens when things go wrong that I'm most interested in...
|
|
Sat Feb 27, 2010 19:48
|
bb400: Thanks Keke,
Obviously error simulation is difficult but, like PDU simulation or modem_disabled simulation, it's very useful in seeing how things work together when it's not all ticking over.
I tried the alarmhandler and got some interesting responses:
modem switched off (ie unresponsive) called alarmhandler unlimited(?) times with sev 3, and my reaction to that would be after X times reboot PC in case it's a serial port problem.
modem switched on gave 'modem busy' sev 2 and this was more worrying because 'the modem handler' failed but smsd didn't recover itself, so I'd assume a sev 2 means restart smsd - but I wondered if the alarm handler can do that, or whether it could kill it's PPID (or whatever) and leave upstart/inittab to respawn.
As far as messages go, I did consider this further for my own use - where messages can have a Failure_code where 1xx signifies smsd is faulty and 2xx signifies the modem/network is faulty and 3xx signifies the message itself is faulty - primarily so that 3xx messages won't be retried (eg no destination) and 2xx can be retried on another queue/modem etc etc. I guess 4xx would be unknown problems (like the file has disappeared mid-sending) and 5xx would be succesful...
I wonder if the alarmhandler could cope with an extra argument if the current 3rd one is already optional, so perhaps leave that as-is and put a failure_code in the file.
|
|
Fri Feb 26, 2010 14:38
|
bb400: Operating system name and version: Ubuntu 9.10
Version of smsd: 3.1.6
Smsd installed from: sources
Name and model of a modem / phone:
Interface:
So far I'm very impressed, the only problems I had turned out to be answered in this forum...
what I'd like to do next is test what happens if there is a modem error, or signal quality error etc.
I realise I can do this by putting the modem in a tin box, or pulling out the sim etc but when I 'grepped' the fail_text I'd like to test each one of these.
Is there an approved way of testing the problem situations?
I'd also like to see a more structured 'error' system whereby errors are given codes rather than 'english' reasons - similar to FTP/HTTP where the code can imply whether the failure is because of the message itself (eg no destination) or a 'temporary' or 'local' fault (eg modem). This would mean a valid message that is rejected because of a signal problem could be picked up by another modem or another smsd...
Thanks,
|
|
Thu Feb 25, 2010 13:40
|
bb400: I wonder if smsd should have it's own 'processing' directory to eliminate problems with (eg) a shared 'outgoing' but also to protect against any other problems.
ie if processdir is defined, then outgoing is mv to processing directory, which ensures it has sufficient rights & access (especially over NFS/sshfs).
if it chokes on the mv then nothing bad happens, but if it chokes on anything and smsd fails then the last message in 'processing' would be the culprit.
Or reverse it, and if 'shareddirectory' is defined it looks there for new files (possibly with a filter) and mv files individually to 'outgoing'...
|
|
Thu Feb 25, 2010 11:47
|
bb400: Thanks Keke
You've raised a good point about the mv since my objective is to run smsd on 2 boxes with a shared 'outgoing' which they can pick up individual messages, and I think a mv from a 'shared' to individual outgoing makes more sense, in which case the filter has to be outside of smsd.
|
|
Wed Feb 24, 2010 16:00
|
bb400: In the meantime I have altered extras.c getfile with:
if (strcmp(tmpname +strlen(tmpname) -5, ".LOCK") != 0)
{
if (strcmp(tmpname +strlen(tmpname) -5, ".smsd") == 0)
{
it seems to work...
|
|
Wed Feb 24, 2010 15:47
|
bb400: Operating system name and version: ubuntu 9.10
Version of smsd: 3.1.6
Smsd installed from: sources
Name and model of a modem / phone: wavecom fastrack
Interface: rs232
Hi,
Is there a file filter on 'outgoing' so only certain files are picked up?
Thanks
|
