Monome Grid & Bela

jonnybela

when connecting and disconnecting it report
root@bela:~# journalctl -f -n 50 -u serialoscd
-- Logs begin at Thu 2016-11-03 17:16:43 UTC. --
Nov 12 07:33:25 bela systemd[1]: Started serialosc daemon.
Nov 14 05:38:25 bela serialoscd[163]: serialosc [m0000606]: connected, server running on port 12088
Nov 14 05:38:31 bela serialoscd[163]: serialosc [m0000606]: couldn't write config to (null) 🙁
Nov 14 05:38:31 bela serialoscd[163]: [-] bad message, bailing out
Nov 14 05:38:31 bela serialoscd[163]: serialosc [m0000606]: disconnected, exiting

jonnybela

Sorry for the day long responses!, im working long hours at the moment...

giuliomoro

hmm did you actually do make install after applying the latest patch? This error message looks identicla to the previous one.

jonnybela

Hi! I just check and did it again. same output

Could this related to any of the messages I get when I run ./waf configure ? When its doing its checking (for compiler etc) everything is reported as yes (in green) however checking for funopen and reallocarray are reported as no (orange) plus checking for header windows.h it reports not found (again, in orange).

Says that the configure was successfully finished so appears okay but did wonder

giuliomoro

jonnybela Could this related to any of the messages I get when I run ./waf configure ? When its doing its checking (for compiler etc) everything is reported as yes (in green) however checking for funopen and reallocarray are reported as no (orange) plus checking for header windows.h it reports not found (again, in orange).

Says that the configure was successfully finished so appears okay but did wonder

that's all good actually. waf tries to figure out what resources are available and if something is optional it will be fine if it's not present. It would fail if anything required was missing.

jonnybela Hi! I just check and did it again. same output

Did you restart the process as well? It doesn't quite make sense because sosc_config_write() is called before couldn't write config to is printed, so the fprintf that we add in there should be printed as well.

Can you show the result of grep sosc_config_write src/serialosc-device/config.c just to make sure the printing is actually there?

Or maybe change the printf in that file to fprintf(stderr, in case there's some magic made to remove stdout but keep stderr.

jonnybela

root@bela:~/serialosc# grep sosc_config_write src/serialosc-device/config.c
sosc_config_write(const char *config_dir, const char *serial, sosc_state_t *state)
printf("sosc_config_write(%s, %s, %p)\n", config_dir ? config_dir : "(null)", serial ? serial : "(null)", state);
root@bela:~/serialosc#

How do I restart the process? I typically run systemctl (start/stop) serialoscd

giuliomoro

jonnybela I typically run systemctl (start/stop) serialoscd

that's right. Try turning those into fprintf then. To avoid confusion, simply checkout the main branch here https://github.com/giuliomoro/serialosc
There, I applied the patches above and turned those printf into fprintf

jonnybela

I get an err changing line to
fprintf(stderr("FOPEN PATH %s\n",path));

I don't know c but assume needed extra brackets in there

jonnybela

or did you mean on this line?
printf("sosc_config_write(%s, %s, %p)\n", config_dir ? config_dir : "(null)", serial ? serial : "(null)", state);

change it to
fprintf(stderr("sosc_config_write(%s, %s, %p)\n", config_dir ? config_dir : "(null)", serial ? serial : "(null)", state));

jonnybela

Gotcha, now when i plugin, plug out
Nov 15 17:12:40 bela serialoscd[195]: serialosc [m0000606]: connected, server running on port 10143
Nov 15 17:12:44 bela serialoscd[195]: sosc_config_write((null), m0000606, 0xbea70c08)
Nov 15 17:12:44 bela serialoscd[195]: FOPEN PATH (null)/.config/serialosc/m0000606.conf
Nov 15 17:12:44 bela serialoscd[195]: serialosc [m0000606]: couldn't write config to (null) 🙁
Nov 15 17:12:44 bela serialoscd[195]: serialosc [m0000606]: disconnected, exiting

giuliomoro

right, so it's not looking into /root/.config but in /.config. What do you get with grep ExecStart /lib/systemd/system/serialoscd.service ?

giuliomoro

giuliomoro What do you get with grep ExecStart /lib/systemd/system/serialoscd.service ?

Can you try this again?

jonnybela

ExecStart=/usr/local/bin/serialoscd

giuliomoro

Guess you missed this:

infinitedigits use it:

ExecStart=/usr/local/bin/serialoscd -c ~/.config/serialosc/

jonnybela

Not quite sure what you mean

typing grep ExecStart /lib/systemd/system/serialoscd.service
only returns
ExecStart=/usr/local/bin/serialoscd

i.e .it doesn't return -c/.config/serialosc

giuliomoro

you need to edit /lib/systemd/system/serialoscd.service and replace

ExecStart=/usr/local/bin/serialoscd

with

ExecStart=/usr/local/bin/serialoscd -c ~/.config/serialosc/

then do systemctl daemon-reload; systemctl restart serialoscd and it should work

jonnybela

mmm, same errors unfortunately

jonnybela

returns
ExecStart=/usr/local/bin/serialoscd -c ~/.config/serialosc/

giuliomoro

And show the new log?

jonnybela

referring to this ?
Nov 15 18:43:28 bela serialoscd[796]: serialosc [m0000606]: connected, server running on port 15591
Nov 15 18:43:32 bela serialoscd[796]: sosc_config_write(~/.config/serialosc/, m0000606, 0xbede1be8)
Nov 15 18:43:32 bela serialoscd[796]: FOPEN PATH ~/.config/serialosc//m0000606.conf
Nov 15 18:43:32 bela serialoscd[796]: serialosc [m0000606]: couldn't write config to ~/.config/serialosc/ 🙁
Nov 15 18:43:32 bela serialoscd[796]: serialosc [m0000606]: disconnected, exiting

« Previous Page