|
Post by finlaydag33k on Oct 5, 2016 15:24:36 GMT
Hii there,
I've installed Automaton on my FruityWifi box. But When I use these settings:
OnStart: - OnStop: - OnBoot: ap-karma-start.conf
only the FruityDNS shows up as "Enabled". (and the config is not the one I entered in the ap-karma-start.conf) However, when I go to the automaton module panel, and click "run" next to ap-karma-start.conf, it all works perfectly fine. Why doesn't it work the way I expect it to when I reboot my raspberry pi?
This is the content of my ap-karma-start.conf:
SET /config/core/ap_mode/4
SET /config/core/io_in_iface/wlan0
SET /config/core/io_out_iface/-
SET /config/core/hostapd_secure/0
SET /config/core/hostapd_ssid/ZekerGeenHotspot
SLEEP 5 START ap
SLEEP 5
START karma
|
|
|
Post by xtr4nge on Oct 6, 2016 7:57:10 GMT
Hi finlaydag33k Glad to know that you are playing with Automaton (I really like this module)
First get the command that is executed on boot from rc.local
cat /etc/rc.local
you will see something like this:
python /usr/share/fruitywifi/www/modules/automaton/includes/client/fruitywifi_client.py -f /usr/share/fruitywifi/www/modules/automaton/includes/templates/ap-karma-start.conf -t YOUR-API-KEY-HERE
run your line from the command line, to be sure that everything is working fine. That should trigger the commands on ap-karma-start.conf
If that works fine, change your config as follows, I added 2 lines to restart nginx and php5-fpm before to run your commands (and run again to confirm that is working fine).
EXEC /etc/init.d/nginx restart EXEC /etc/init.d/php5-fpm restart
SLEEP 2
SET /config/core/ap_mode/4 SET /config/core/io_in_iface/wlan0 SET /config/core/io_out_iface/- SET /config/core/hostapd_secure/0 SET /config/core/hostapd_ssid/ZekerGeenHotspot
SLEEP 5 START ap
SLEEP 5 START karma
Some devices needs more sleep time before to start the AP and Karma, try increasing the SLEEP time to 10 or 15 seconds if needed.
let me know regards,
|
|
|
Post by finlaydag33k on Oct 6, 2016 8:46:14 GMT
I think I figured out what was going wrong. when I do cat /etc/rc.local it says: <all kinds of paths> and then -f <path>/ap-start.conf I changed this to ap-karma-start.conf and now it seems to run fine I don't know why, but it seems that it didn't update the rc.local properly.
|
|
|
Post by xtr4nge on Oct 6, 2016 10:29:43 GMT
Cool Do a few tests changing the on-boot conf file, disable and enable on-boot, and cat rc.local to be sure that is changing . The line on rc.local changes when on-boot is re-enabled regards,
|
|
|
Post by finlaydag33k on Oct 6, 2016 10:52:29 GMT
Will do, and if I see an issue in the module itself (which causes it) I will make a pull on the github
|
|
|
Post by xtr4nge on Oct 6, 2016 11:08:20 GMT
Will do, and if I see an issue in the module itself (which causes it) I will make a pull on the github Awesome, thanks
|
|
|
Post by finlaydag33k on Oct 6, 2016 12:53:29 GMT
Okay, I think i know what the issue may have been.
when I edit the config to use (for example change `ap-karma-start.conf` to `ap-start.conf`) nothing happens by default. however, when you restart the OnBoot part, it will update.
so it acts like this:
edit config -> manually restart OnBoot part -> /etc/rc.local gets updated -> reboot machine -> selected OnBoot config runs
I don't know if this is intended or not, so I won't fix it just yet. but wouldn't it be better to have it like this (to minimize confusion?):
edit config -> /etc/rc.local gets updated -> reboot machine -> selected OnBoot config runs
|
|
|
Post by xtr4nge on Oct 6, 2016 13:06:01 GMT
Hi finlaydag33k, yes, that is intended, the line on rc.local changes when on-boot is re-enabled from Automaton module regards,
|
|
|
Post by finlaydag33k on Oct 6, 2016 13:14:28 GMT
ah okay, then it's no bug but just me expecting too much xD
|
|