ade
|
2011-12-18
, 23:06
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#871
|
|
2011-12-19
, 00:04
|
|
Posts: 1,648 |
Thanked: 2,122 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#872
|
OK, I'll upload log in few minutes. Meanwhile, another thing (although, I'm not sure if it is a bug, or a feature ) - selecting "send reply messages on" 'battery status' and ''slide open'', result in (after reboot) message containing battery status /indicating that slide was open even though SIM *wasn't* replaced by one with different IMSI. Which, I think, kill purpose of this command.
Requested log:
...
// edit
Another minor mistake (?) in SMSCON editor - On tab "general", under "Mobile number of contact" (aka masternumber) is:
AFAIU, it's not true - masternumber doesn't change, SMS is just sent twice.Code:*will change on first command
Also, another observation - after testing sms message, I got *two* messages with "test message", and also *two* messages with fatal error - hence the feeling of being spammed. In fact, it's only 4 messages instead of 1 (no irony, just trying to be specific).
+feature upgrade request:
Allowing to start (remotely) reverse ssh is great option, but, AFAIK, now it works only with ssh connection with password authentication. could You, please, implement authorisation via public key - preferably, located @ configurable (from SMSCON editor) path?
The idea is, to create special private/public key part, only for using it with SMSCON. normally, sane usage of public key authentication on mobile device require locking it with password - so, no way to use it remotely, as there is no one on the device to write password - but, special pubkey without password just for SMSCON (thus, creating connection with limited access), would be nice to have.
/Estel
The Following User Says Thank You to Saturn For This Useful Post: | ||
|
2011-12-19
, 00:46
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#873
|
I also don't like this option and I never use it
The original idea is to get a message everytime the battery drops one bar.
I will discuss it with the others and try to convince them to change it to send a message only when below a threshold.
Unfortunately the log doesn't have much valuable info.
Could you try the same sequence as before but with the "Retry on failed reply message" to OFF (unchecked)?
I would like to see if the -fatal error- disappears that way.
(...)
I was curious for the log to understand where the code to stop sending messages when it crashes failed. Apparently it hasn't failed and it stopped sending.
The thing is I cannot reproduce a failed send message to check the code. I have sent literally hundreds of SMS and all were sent correctly.
2011-12-19 01:34:45[SMSCON] INFO: Export to user setting file "/home/user/.smscon-editor/smscon_config" successful. 2011-12-19 01:34:51[SMSCON] INFO: Daemon smscon_daemon was not running. 2011-12-19 01:34:52[SMSCON] INFO: "SMS" TEST BEGINS -------------- 2011-12-19 01:34:52[SMSCON] INFO: Daemon smscon_daemon requested to start -test "sms" . 2011-12-19 01:34:52[SMSCON] INFO: "SMS" TEST: Daemon smscon_daemon now active. 2011-12-19 01:34:53[DAEMON] CRITICAL: smscon_daemon is starting. 2011-12-19 01:34:53[DAEMON] INFO: Successfully loaded "/opt/smscon/smscon_config" file. 2011-12-19 01:34:53[DAEMON] INFO: Found 1 IMSI code(s) in "/opt/smscon/smscon_code" file. 2011-12-19 01:34:53[DAEMON] INFO: Authorized IMSI code found. 2011-12-19 01:34:53[DAEMON] WARNING: smscon does not auto-load at boot. 2011-12-19 01:35:10[DAEMON] ERROR: Failed to send SMS to "+XXXXXXXXXXX". 2011-12-19 01:35:10[DAEMON] INFO: (EMAIL) Trying to connect to "smtp.gmail.com:587" (2011-12-19 01:35:10). 2011-12-19 01:35:10[DAEMON] INFO: (EMAIL) Trying to login to "smtp.gmail.com". 2011-12-19 01:35:11[DAEMON] INFO: (EMAIL) Trying to send email to "smtp.gmail.com". 2011-12-19 01:35:13[DAEMON] INFO: send email message (subject=boot) to <mail@gmail.com> 2011-12-19 01:35:13[DAEMON] INFO: (EMAIL) Mailserver connection closed successful. 2011-12-19 01:35:13[DAEMON] INFO: Phone battery charge is 52%, discharging. 2011-12-19 01:35:30[DAEMON] ERROR: Failed to send SMS to "+XXXXXXXXXXX". 2011-12-19 01:35:30[DAEMON] INFO: Keyboard slider change detection is on. 2011-12-19 01:35:31[DAEMON] INFO: Battery status change detection is on. 2011-12-19 01:35:31[DAEMON] INFO: (CHECKHOST) Checkhost is off.
N900[BloodRose] 2011-12-19 01:34:53 -boot- smscon does not auto-load at boot.
The Following User Says Thank You to Estel For This Useful Post: | ||
|
2011-12-19
, 15:38
|
Posts: 2 |
Thanked: 4 times |
Joined on Dec 2011
|
#874
|
The Following User Says Thank You to sdmech For This Useful Post: | ||
|
2011-12-19
, 15:54
|
|
Posts: 1,648 |
Thanked: 2,122 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#875
|
Firstly if this has been already commented on and i have missed it then sorry for the double post.
I updated smscon and its editor today.
Since the update the smscon editor will not open.
I get
value of user setting of user setting "checkhost" does not match
then i get
Loading active settings failed
failed to activate recent edit settings
Activating initial settings failed
then i get the same message again, and then i get
Enforcedly loaded smscon settings
Please check them all.some seem to be invalid
and it closes.
I have read the thread and i have uninstalled both parts then re-installed them again, and it makes no difference.
This is a fantastic app and i hope it can be fixed.
rm -rf /opt/smscon/ rm -rf /opt/smscon-editor/ rm -rf /home/user/.smscon-editor rm -f /usr/bin/smscon-editor
|
2011-12-19
, 22:51
|
Posts: 27 |
Thanked: 12 times |
Joined on Sep 2010
@ Paris
|
#876
|
CHECKHOST = 'www.bla.com/filetocheck'
The Following User Says Thank You to Julien_2006 For This Useful Post: | ||
|
2011-12-19
, 22:52
|
|
Posts: 1,648 |
Thanked: 2,122 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#877
|
I am sorry to say that we are back where we started from. I followed your instructions and still after the reboot I get the sms for change of SIM and the one one gps location, plus the red permanent charger's light.
...
rm -rf /opt/smscon/ rm -rf /opt/smscon-editor/ rm -rf /home/user/.smscon-editor rm -f /usr/bin/smscon-editor rm -f /usr/bin/smscon rm -f /etc/sudoers.d/smscon.sudoers rm -f /etc/sudoers.d/smscon-editor.sudoers rm -f /etc/event.d/smscon_boot update-sudoers
The Following User Says Thank You to Saturn For This Useful Post: | ||
|
2011-12-19
, 23:40
|
Posts: 155 |
Thanked: 315 times |
Joined on Jun 2010
@ DE
|
#878
|
Hi I just downloaded smscon but can't seem to get access to it.
smscon -start returns ERROR: smscon must be run as "root"
am I missing something?
thanks
$ sudo smscon -start
|
2011-12-20
, 00:26
|
Posts: 155 |
Thanked: 315 times |
Joined on Jun 2010
@ DE
|
#879
|
Hi,
I made the 'fatal' mistake to change my SIM card while having SMSCON installed. After several unsuccessful attempts to bring things back to normal through the SMSCON editor, I still received those sms's regarding the SIM and the GPS location of the phone on every single reboot.
Finally I gave up and removed both SMSCON, the editor, plus the opt/... and etc/inti.d paths. It was futile. My N900 still thinks I am the thief and keeps sending to itself sms's.
Please let me know how to get rid of the SMSCON ghost!
rm -f /usr/bin/smscon rm -f /etc/sudoers.d/smscon.sudoers rm -f /etc/event.d/smscon_boot rm -rf /opt/smscon update-sudoers gtk-update-icon-cache -f /usr/share/icons/hicolor # reboot the phone to finally kill the "ghost": reboot
|
2011-12-20
, 01:37
|
Posts: 155 |
Thanked: 315 times |
Joined on Jun 2010
@ DE
|
#880
|
OK, I've installed new version and configured it. Upon using "test" page (SMS) I got "Nokia N900 test message" correctly, but just after receiving it, SMSCON started to spam masternumber with SMS messages with content:
I had to killall smscon_daemon to stop sending SMS'esCode:-fatal error- smscon_daemon crashed. only 'priority' keyword argument accepted
If I can provide more info that will help debugging this issue, just point me what to do.
/Estel
// Edit
Same message also appeared on e-mail (I've used "both" sms and email as receiver), although only once (no spam as with SMS).