[Announce] SMScon (control your device with SMS) - Page 94 - maemo.org

Active Topics

The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 11 hrs, 30 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 7 hrs ago
more...

Page 94 of 130

Thread Tools

yablacky	2011-12-25 , 12:48
Posts: 155 \| Thanked: 315 times \| Joined on Jun 2010 @ DE	#931

Originally Posted by ade

So the source code is available? In the garage, I only saw the deb files (and no tar.gz source).

My installed version is: 0.9.6

OK, please in xterm enter following (as normal user):

Code:

$ smscon -stop
    ##expected output is like:
    INFO: Daemon smscon_daemon stopped [PID=6152].
    INFO: Script smscon_script was not running.

$ smscon -stop
    ##expected output is like:
    INFO: Daemon smscon_daemon was not running.
    INFO: Script smscon_script was not running.

$ smscon -start
    ##expected output is like:
    INFO: Daemon smscon_daemon requested to start.
    INFO: Daemon smscon_daemon started [PID=7774].

    #in the above case all should be well. But if output is different
    ##  and has error message - and in your case it probably has - 
    ## then enter:

$ ps > ps.txt

   ## Please post the ps.txt file here.

Since we manage source in repository, we've been lazy in uploading packages to garage, sorry. Source for 0.9.6 can be found here: http://maemo.org/packages/source/vie...mscon/0.9.6-2/

Quote & Reply |

The Following User Says Thank You to yablacky For This Useful Post:
Saturn

	Saturn	2011-12-25 , 13:05
	Posts: 1,648 \| Thanked: 2,122 times \| Joined on Mar 2007 @ UNKLE's Never Never Land	#932

Originally Posted by ade

Since I got no response to http://talk.maemo.org/showpost.php?p...&postcount=893 I wanted to look in the code myself.
But the program itself is compiled python an there is no source code available. Perhaps it is because of security reasons, but it makes tracking problems not that easy. Is it possible to get some levels of debug logging available instead? Just the message "ERROR: Daemon smscon_daemon failed to start." in the log doesn't give me a clue...

Just wanted to add

- The code is delivered in human readable/normal python format and is being compiled during installation. So extracting the deb files will give the full code.

- The tar files you can find them (similar case for all of the free distribution packages) in http://maemo.org/packages/view/smscon/

- The SVN in Garage is set to open/anonymous access.

I hope it is clear the source code has always been open and available.

Merry Christmas to all

__________________
Packages: elGR Locale, SMSCON Editor, Swappolube, CSSU Features Configuration, Snuggle, YAMAS, Cleven
Garage: SMSCON, Swappolube, CSSU Features Configuration, Snuggle
Wiki: SMSCON, SMSCON Editor, Swappolube, CSSU Features Configuration, Cleven

Quote & Reply |

The Following 5 Users Say Thank You to Saturn For This Useful Post:
ade, bocephus, ejasmudar, The Winter, yablacky

ade	2011-12-25 , 13:28
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#933

[QUOTE=yablacky;1141687]OK, please in xterm enter following (as normal user):

Code:

$ smscon -stop
    ##expected output is like:
    INFO: Daemon smscon_daemon stopped [PID=6152].
    INFO: Script smscon_script was not running.

$ smscon -stop
    ##expected output is like:
    INFO: Daemon smscon_daemon was not running.
    INFO: Script smscon_script was not running.

$ smscon -start
    ##expected output is like:
    INFO: Daemon smscon_daemon requested to start.
    INFO: Daemon smscon_daemon started [PID=7774].

    #in the above case all should be well. But if output is different
    ##  and has error message - and in your case it probably has - 
    ## then enter:

$ ps > ps.txt

   ## Please post the ps.txt file here.

output:

Code:

user:~# smscon -stop
INFO: Daemon smscon_daemon was not running.
INFO: Script smscon_script was not running.
user:~# smscon -start
INFO: Daemon smscon_daemon requested to start.
ERROR: Daemon smscon_daemon failed to start.

I already added the relevant process list in http://talk.maemo.org/showpost.php?p...&postcount=898

Thanks for the link to the code, maybe it gives me a clue.

Quote & Reply |

	Saturn	2011-12-25 , 13:51
	Posts: 1,648 \| Thanked: 2,122 times \| Joined on Mar 2007 @ UNKLE's Never Never Land	#934

@ade,

Do you have a SIM card in?

And why you don't post your log?

Quote & Reply |

ade	2011-12-25 , 14:08
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#935

I do have a simcard inserted.

The log does not provide much extra information:

Code:

2011-12-25 14:39:29[DAEMON] INFO: (EMAIL) Mailserver connection closed successful.
2011-12-25 14:39:30[DAEMON] INFO: Phone battery charge is 70%, discharging.
2011-12-25 14:39:30[DAEMON] INFO: Keyboard slider change detection is off.
2011-12-25 14:39:30[DAEMON] INFO: Battery status change detection is off.
2011-12-25 14:39:30[DAEMON] INFO: (CHECKHOST) Checkhost is off.
2011-12-25 14:39:32[SMSCON] INFO: Daemon smscon_daemon was not running.
2011-12-25 14:39:33[SMSCON] INFO: Script smscon_script was not running.
2011-12-25 14:43:11[SMSCON] INFO: Daemon smscon_daemon was not running.
2011-12-25 14:43:11[SMSCON] INFO: Script smscon_script was not running.
2011-12-25 14:47:59[SMSCON] INFO: Daemon smscon_daemon requested to start.
2011-12-25 14:48:00[DAEMON] CRITICAL: smscon_daemon is starting.
2011-12-25 14:48:00[SMSCON] ERROR: Daemon smscon_daemon failed to start.
2011-12-25 14:48:00[DAEMON] INFO: Successfully loaded "/opt/smscon/smscon_config" file.
2011-12-25 14:48:00[DAEMON] INFO: Found 1 IMSI code(s) in "/opt/smscon/smscon_code" file.
2011-12-25 14:48:00[DAEMON] INFO: Authorized IMSI code found.
2011-12-25 14:48:01[DAEMON] WARNING: smscon does not auto-load at boot.

Looking at the code gives me the impression it cannot determine the pids (pidof) correctly, because it starts a daemon, but cannot see it afterwards.

Quote & Reply |

yablacky	2011-12-25 , 14:09
Posts: 155 \| Thanked: 315 times \| Joined on Jun 2010 @ DE	#936

Originally Posted by ade

output:
Code:
user:~# smscon -stop
INFO: Daemon smscon_daemon was not running.
INFO: Script smscon_script was not running.
user:~# smscon -start
INFO: Daemon smscon_daemon requested to start.
ERROR: Daemon smscon_daemon failed to start.
I already added the relevant process list in http://talk.maemo.org/showpost.php?p...&postcount=898

Thanks for the link to the code, maybe it gives me a clue.

It seems that the error is not that the daemon did not start. The error is that something is wrong in detecting that the daemon got started. Because in the ps list you posted, it seems to be there, even more than once (which is ok but normally should not happen).

So we have to find out why the detection of specific processes in the process list does not work on your device.

Could you please do the following: check if ps shows a process like "python /opt/smscon/smscon_daemon". Then enter (as normal user)

Code:

$ pidof /opt/smscon/smscon_daemon
    ### expected empty result
    # then:
$ ps | grep -v grep | grep /opt/smscon/smscon_daemon
    ### expected something like
    7774 root     15684 S    python /opt/smscon/smscon_daemon

Should you get any other than the expected output please let me know exactly which output you got.

Quote & Reply |

yablacky	2011-12-25 , 14:12
Posts: 155 \| Thanked: 315 times \| Joined on Jun 2010 @ DE	#937

Originally Posted by ade

... Looking at the code gives me the impression it cannot determine the pids (pidof) correctly, because it starts a daemon, but cannot see it afterwards.

Yes, I had the same idea and that's why I asked for the ps list

But see my last post.

Quote & Reply |

ade	2011-12-25 , 14:29
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#938

Originally Posted by yablacky

It seems that the error is not that the daemon did not start. The error is that something is wrong in detecting that the daemon got started. Because in the ps list you posted, it seems to be there, even more than once (which is ok but normally should not happen).

So we have to find out why the detection of specific processes in the process list does not work on your device.

Could you please do the following: check if ps shows a process like "python /opt/smscon/smscon_daemon". Then enter (as normal user)
Code:
$ pidof /opt/smscon/smscon_daemon
    ### expected empty result
    # then:
$ ps | grep -v grep | grep /opt/smscon/smscon_daemon
    ### expected something like
    7774 root     15684 S    python /opt/smscon/smscon_daemon
Should you get any other than the expected output please let me know exactly which output you got.

You are doing the "ps" diffently than I do. Maybe that is because you use an alias? A ps will only output your shell and ps itself.
When I add "-ef" to ps, I get:

Code:

root     17181     1  2 15:22 pts/1    00:00:00 python /opt/smscon/smscon_daemon

The pidof has indeed an empty result (because python itself is the process holder)

Quote & Reply |

The Following User Says Thank You to ade For This Useful Post:
yablacky

yablacky	2011-12-25 , 14:44
Posts: 155 \| Thanked: 315 times \| Joined on Jun 2010 @ DE	#939

Originally Posted by ade

You are doing the "ps" diffently than I do. Maybe that is because you use an alias? A ps will only output your shell and ps itself.
When I add "-ef" to ps, I get:
Code:
root     17181     1  2 15:22 pts/1    00:00:00 python /opt/smscon/smscon_daemon
The pidof has indeed an empty result (because python itself is the process holder)

Hey, ade, thank you, that'it! You have an extended "ps" on your machine. The standard ps is a symlink to busybox which does not care for options and always prints the full list.

Have fixed it for the next release.

Quote & Reply |

The Following User Says Thank You to yablacky For This Useful Post:
ade

ade	2011-12-25 , 14:53
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#940

Originally Posted by yablacky

Hey, ade, thank you, that'it! You have an extended "ps" on your machine. The standard ps is a symlink to busybox which does not care for options and always prints the full list.

Have fixed it for the next release.

Good thinking yablacky!

I have installed bash and gnu tools, maybe that has overwritten the ps symlink, because I am not aware I have replaced ps for a non busybox one.

Merry Christmas for the remainer of the day