Schmill Posted February 14, 2014 Share #1 Posted February 14, 2014 Does anyone know what synorelayd is, or what it might be trying to do on my system? I realised that my drive(s) didn't seem to be spinning down anymore, and checking /var/log/messages reveals pages and pages of the following entry: Feb 14 00:04:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:14:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:24:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:34:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:44:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:54:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:04:29 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:14:29 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:24:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:34:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:44:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:54:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:04:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:15:28 scemd: write to uart2 error, error=(5)Input/output error Feb 14 02:19:50 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:35:23 synorelayd[7871]: synorelayd.cpp:577 regist stop: relayd_err: 2 (52) Feb 14 02:35:42 scemd: write to uart2 error, error=(5)Input/output error Feb 14 02:45:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:55:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:05:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:15:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:25:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:35:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:45:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:55:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:05:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:15:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:25:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:35:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:45:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:55:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 05:05:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 05:15:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error I'm not sure what the uart errors are about, but I'm presuming that the original DS hardware has something connected to it via serial that is not available on the N54L. However the major issue here does seem to be the synorelayd entries.... but I have no idea what they are referring to, so don't know what I can do about it. Any ideas anybody? Also this obviously refers to a particular line in a source file of the DSM system... but where can I get the source? I wouldn't mind a look through it myself.... Thanks again! Link to comment Share on other sites More sharing options...
Schmill Posted February 14, 2014 Author Share #2 Posted February 14, 2014 Does anyone know what synorelayd is, or what it might be trying to do on my system? I realised that my drive(s) didn't seem to be spinning down anymore, and checking /var/log/messages reveals pages and pages of the following entry: Feb 14 00:04:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:14:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:24:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:34:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:44:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 00:54:28 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:04:29 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:14:29 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:24:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:34:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:44:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 01:54:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:04:30 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:15:28 scemd: write to uart2 error, error=(5)Input/output error Feb 14 02:19:50 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:35:23 synorelayd[7871]: synorelayd.cpp:577 regist stop: relayd_err: 2 (52) Feb 14 02:35:42 scemd: write to uart2 error, error=(5)Input/output error Feb 14 02:45:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 02:55:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:05:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:15:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:25:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:35:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:45:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 03:55:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:05:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:15:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:25:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:35:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:45:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 04:55:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 05:05:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error Feb 14 05:15:23 synorelayd[7871]: synorelayd.cpp:563 regist command auth error I'm not sure what the uart errors are about, but I'm presuming that the original DS hardware has something connected to it via serial that is not available on the N54L. However the major issue here does seem to be the synorelayd entries.... but I have no idea what they are referring to, so don't know what I can do about it. Any ideas anybody? Also this obviously refers to a particular line in a source file of the DSM system... but where can I get the source? I wouldn't mind a look through it myself.... Thanks again! Link to comment Share on other sites More sharing options...
goddamnit Posted February 14, 2014 Share #3 Posted February 14, 2014 It's cloud station Link to comment Share on other sites More sharing options...
goddamnit Posted February 14, 2014 Share #4 Posted February 14, 2014 It's cloud station Link to comment Share on other sites More sharing options...
Schmill Posted February 14, 2014 Author Share #5 Posted February 14, 2014 I only have the following installed though.... Audio Station Download Station Media Server Video Station No Cloud Station installed at all, let alone running... Link to comment Share on other sites More sharing options...
Schmill Posted February 14, 2014 Author Share #6 Posted February 14, 2014 I only have the following installed though.... Audio Station Download Station Media Server Video Station No Cloud Station installed at all, let alone running... Link to comment Share on other sites More sharing options...
Schmill Posted February 22, 2014 Author Share #7 Posted February 22, 2014 It seems the number in the square brackets is a red herring, as it is now a different number, seems the only relevant bit is the '563' which I presume is the line number generating the error. I have now killed and restarted the deamon in debug mode (synorelay -k, closely following by synorelayd -d and I get the following: synorelayd -d success -> starting Feb 22 17:13:30 2014 daemon.cpp:379 daemon start success -> login Feb 22 17:13:30 2014 register.cpp:57 register clear previous data Feb 22 17:13:30 2014 register.cpp:287 check: audio_http Feb 22 17:13:30 2014 register.cpp:287 check: audio_https add request: https://ukc.synology.com:443/Serv.php [{"auth":{"mac":"<>","serial":"<>","timezone":"Dublin","token":"<>"},"command":"register","version":1},{"command":"update_network","ddns":"<>","gateway":"192.168.22.1","interface":[{"ip":"192.168.22.10","mask":"255.255.255.0","name":"eth0"}],"mode":"","version":1},{"command":"update_service","service_add":[{"id":"audio_http","port":5000},{"id":"audio_https","port":5001}],"service_rm":[],"service_update":[],"version":1}] Feb 22 17:13:30 2014 synorelayd.cpp:874 select 10... Feb 22 17:13:30 2014 jobqueue.cpp:201 queue check done jobs. running: 1 (1) tunnel[0]: Feb 22 17:13:30 2014 synorelayd.cpp:874 select 10... Feb 22 17:13:30 2014 jobqueue.cpp:201 queue check done jobs. running: 1 (1) tunnel[0]: Feb 22 17:13:30 2014 synorelayd.cpp:874 select 10... Feb 22 17:13:30 2014 jobqueue.cpp:201 queue check done jobs. running: 1 (1) tunnel[0]: Feb 22 17:13:30 2014 synorelayd.cpp:874 select 10... Feb 22 17:13:30 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) ===> register response: (0)[{"version":1,"command":"register","errno":2,"errinfo":"RegDS.php:230"}] [AUTH]err_auth Feb 22 17:13:30 2014 synorelayd.cpp:203 save php session Feb 22 17:13:30 2014 synorelayd.cpp:563 regist command auth error err_auth -> login Feb 22 17:13:30 2014 synorelayd.cpp:704 auth expired: 1, server chagned: 0 Feb 22 17:13:30 2014 register.cpp:57 register clear previous data Feb 22 17:13:30 2014 register.cpp:287 check: audio_http Feb 22 17:13:30 2014 register.cpp:287 check: audio_https err_auth -> stoped tunnel[0]: Feb 22 17:13:30 2014 synorelayd.cpp:874 select 10... Feb 22 17:13:40 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) tunnel[0]: Feb 22 17:13:40 2014 synorelayd.cpp:874 select 10... Feb 22 17:13:50 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) tunnel[0]: Feb 22 17:13:50 2014 synorelayd.cpp:874 select 10... Feb 22 17:14:00 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) tunnel[0]: Feb 22 17:14:00 2014 synorelayd.cpp:874 select 10... Feb 22 17:14:10 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) tunnel[0]: Feb 22 17:14:10 2014 synorelayd.cpp:874 select 10... Feb 22 17:14:20 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) tunnel[0]: Feb 22 17:14:20 2014 synorelayd.cpp:874 select 10... Feb 22 17:14:30 2014 jobqueue.cpp:201 queue check done jobs. running: 0 (1) tunnel[0]: Looks like the particular bit of interest is this: ===> register response: (0)[{"version":1,"command":"register","errno":2,"errinfo":"RegDS.php:230"}] [AUTH]err_auth Feb 22 17:13:30 2014 synorelayd.cpp:203 save php session Feb 22 17:13:30 2014 synorelayd.cpp:563 regist command auth error err_auth -> login Feb 22 17:13:30 2014 synorelayd.cpp:704 auth expired: 1, server chagned: 0 Other than the 'built-in' spelling mistakes, it looks like it is when the server is trying to do some kind of registration, but I have no idea what this is. I've changed my DDNS at sinology and noip to be every 30 mins, and yet this 'error' still occurs every 10 minutes... Any idea on what the server is trying to do every ten minutes? I did check /etc/crontab but I couldn't see anything listed in there. Thanks for any information Link to comment Share on other sites More sharing options...
Schmill Posted February 24, 2014 Author Share #8 Posted February 24, 2014 Just in case anyone is following this, I have now solved it It seems that the 'QuickConnect' option had been turned on for DSAudio ("Control Panel" --> "Quick Connect"). However it seems that THAT requires Cloud Station to be installed, which I do not have. Disabling the 'QuickConnect' option for DSAudio has stopped the error in the messages log, and my drives now seem to spin down as they are supposed to However, now that the 'noise' is gone from my messages log, I can see these entries: Feb 24 11:42:26 scemd: write to uart2 error, error=(5)Input/output error Feb 24 11:59:12 scemd: write to uart2 error, error=(5)Input/output error Feb 24 12:39:14 scemd: write to uart2 error, error=(5)Input/output error Feb 24 13:11:53 scemd: write to uart2 error, error=(5)Input/output error Feb 24 17:37:50 scemd: write to uart2 error, error=(5)Input/output error Feb 24 19:01:34 scemd: write to uart2 error, error=(5)Input/output error Presumably that is a side-effect of running the DSM on an N54L (which I don't believe has any UARTS, but what is it trying to do, (or how would I go about finding out?) Thanks Link to comment Share on other sites More sharing options...
stanza Posted February 25, 2014 Share #9 Posted February 25, 2014 It's trying to write to the LCD screen Which naturally it doesn't have . Link to comment Share on other sites More sharing options...
Schmill Posted February 25, 2014 Author Share #10 Posted February 25, 2014 Aha If you don't mind me asking, how do you know that? Also, is there anyway to tell it not to bother? - lol Link to comment Share on other sites More sharing options...
stanza Posted February 26, 2014 Share #11 Posted February 26, 2014 Aha If you don't mind me asking, how do you know that? Also, is there anyway to tell it not to bother? - lol Because when I was trying to get HA working, you could see it was failing with that error So I gather when the REAL Synologies are setup in HA mode....then the LCD's change to reflect the STATUS or Name or IP Address or Master / Slave etc of the HA setup. . Link to comment Share on other sites More sharing options...
anthonyuk Posted February 27, 2014 Share #12 Posted February 27, 2014 I see this is x-posted on the Synology forum Link to comment Share on other sites More sharing options...
Schmill Posted February 28, 2014 Author Share #13 Posted February 28, 2014 Aha If you don't mind me asking, how do you know that? Also, is there anyway to tell it not to bother? - lol Because when I was trying to get HA working, you could see it was failing with that error So I gather when the REAL Synologies are setup in HA mode....then the LCD's change to reflect the STATUS or Name or IP Address or Master / Slave etc of the HA setup. . That makes sense except.... what is "HA mode" ? - lol - Thanks I see this is x-posted on the Synology forum Yup, as I was unsure as to whether it was an XPenology issue, or an underlying Synology issue - Turns out it was Synology Link to comment Share on other sites More sharing options...
anthonyuk Posted March 3, 2014 Share #14 Posted March 3, 2014 Turns out it was Synology Really?? It would work fine if your build wasn't missing the LCD panel? Link to comment Share on other sites More sharing options...
stanza Posted March 3, 2014 Share #15 Posted March 3, 2014 Aha If you don't mind me asking, how do you know that? Also, is there anyway to tell it not to bother? - lol Because when I was trying to get HA working, you could see it was failing with that error So I gather when the REAL Synologies are setup in HA mode....then the LCD's change to reflect the STATUS or Name or IP Address or Master / Slave etc of the HA setup. . That makes sense except.... what is "HA mode" ? - lol - Thanks I see this is x-posted on the Synology forum Yup, as I was unsure as to whether it was an XPenology issue, or an underlying Synology issue - Turns out it was Synology HA = High Availability eg Have 2 x Synologies act as one in case one dies . Link to comment Share on other sites More sharing options...
Recommended Posts