1. Home
  2. Omega Talk
  3. onion omega2S Struct is happening

onion omega2S Struct is happening

  • N

    @crispyoz
    I am running onion omega2s bord using 3.5V power supply and without power interrupt purpose i have connected 3.7V battery 2200 mah current. I used in between a Diode. Diode passing voltage as 3.5V. When i run firmware inside onion it has run a few days, after few days suddenly my onion omega has struct but voltage it's there in onion omega. So what could be the problem?.

    crispyoz sir, you said it won't make any problem and all.

    0
  • C

    @Nagarjuna-Reddy we could only guess at the reason, but first you need to determine if this is a hardware issue or a software issue.

    First step is to look in the logs and see what was going on at the time the device stopped. I prefer to use remote logging myself so I can monitor multiple devices easily. Look at my post on this thread on how to set that up:

    https://community.onion.io/topic/3649/enabling-netconsole/5?_=1602234193060

    Of course you will need a machine to to receive the logging.

    Is this a repeatable issue? Does the device hang each few days? Do you have more than one device? If you have more than one device do they both exhibit this problem?

    0 N 3 Replies
  • N

    @crispyoz
    Hi sir,
    does onion omega support watchdog timer?. If it supports how to do?

    0
  • C

    @Nagarjuna-Reddy I think this is the definitive article:

    http://kernelreloaded.com/manually-controlling-openwrt-hardware-watchdog/

    But using watchdog may just be a workaround for an underlying issue. Based up on the information you have provided thus far, it is hard to know where your issue is so it would be better to respond to our questions in detail and maybe we can fix the underlying issue.

    0 N 1 Reply
  • N

    @crispyoz
    Hi sir,
    I tried to taking logs but i am not able to getting. Could you please help me, whether i am doing proper way or not?

    Host: 192.168.1.27 is my onion IP.
    Host: 192.168.1.21 is my computer IP.
    udp-1.PNG udp.PNG

    0
  • N

    @crispyoz
    Sir, i am able to taking device logs. Thanks sir.

    one more question i am not able to set it-up watchdog timer as 24 hours. i want my onion to be reboot every 24 hours with the help of watchdog timer.
    i did it below description but it's not happening. It has taken only 60 seconds.
    **# Change timeout to 24 hours
    ubus call system watchdog '{ "timeout": 86400 }'

    Change frequency to 1s

    ubus call system watchdog '{ "frequency": 1 }'

    ubus call system watchdog '{"magicclose": true}'
    ubus call system watchdog '{ "stop": true }'
    echo 1 > /dev/watchdog**

    0
  • C

    @Nagarjuna-Reddy You really shouldn't need to reboot your device every 24 hours, we are not using windows šŸ™‚

    Watchdog is not designed for a scheduled reboot, its purpose is to monitor if main process(s) are responding and depending on that outcome it may or may not reset the device.

    If you want to reboot every 24 hours just use cron, which is designed to perform actions by schedule.

    My sense is that you are trying to work around a problem rather than identifying the root cause. In my experience you are going to spend a lot more time dealing with workarounds than you would identifying the root cause. If you need help please provide more specific details and maybe we can help you in this endeavour.

    0 N 2 Replies
  • N

    @crispyoz
    sir, i am worried about today i have to release onion omega board to productionšŸ˜¢ . but I am facing onion suddenly stopping working when any sudden interrupt happens. So that's why i asked watchdog timer.

    if any OS is struct also watchdog timer can do a restart but crontab can't do right? if anything is a struct or something happens at least after 24 hours board will get recover or come into online using this watchdog timer.

    yesterday i observed another interrupt, that is when i connected 4G sim making PPP connection using modem it's working fine but same thing 2G sim When i connected immediately board is getting restarted and it's not showing active. I tried to ping IP address of the board. It's saying network unreachable.

    Sir, you told me to watch logs. at least board is not turned ON it's full restarting and suddenly struct is happening. How i can watch the logs. Device showing fully offline even IP also i am not able to pinging.

    I am using version 0.3.2 b221. Is this making any problem?

    onion side 3.3V it's showing. I don't have serial USB debugger option if i have at least i can watch what's is going on when device boot-up.

    @crispyoz sir you are the only right person to solve my issue. I am believing you. could you please help me to solve this issue?

    0
  • N

    @crispyoz
    Hi sir, I took logs that i added in below can you fell free to check it once.
    main-problem.PNG

    UDP socket deleted
    UDP socket created
    <30>Oct 13 10:27:31 Omega-7E32 logread[2106]: Logread connected to 192.168.1.21:514<30>Oct 13 10:27:31 Omega-7E32 procd: - init complete -<27>Oct 13 10:27:36 Omega-7E32 uhttpd[2205]: Error: Invalid directory /www: No such file or directory<84>Oct 13 10:27:36 Omega-7E32 dropbear[2173]: Bad password attempt for 'root' from 192.168.1.21:59168<85>Oct 13 10:27:40 Omega-7E32 dropbear[2173]: Password auth succeeded for 'root' from 192.168.1.21:59168<27>Oct 13 10:27:41 Omega-7E32 uhttpd[2214]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:27:46 Omega-7E32 uhttpd[2216]: Error: Invalid directory /www: No such file or directory<30>Oct 13 10:27:46 Omega-7E32 procd: Instance uhttpd::instance1 s in a crash loop 6 crashes, 1 seconds since last crash<29>Oct 13 10:28:22 Omega-7E32 netifd: Interface 'loopback' is now down<29>Oct 13 10:28:22 Omega-7E32 netifd: Interface 'loopback' is disabled<29>Oct 13 10:28:22 Omega-7E32 netifd: Network device 'lo' link is down<29>Oct 13 10:28:22 Omega-7E32 netifd: Interface 'loopback' has link connectivity loss<30>Oct 13 10:28:30 Omega-7E32 logread[2106]: Logread connected to 192.168.1.21:514<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: abort on (BUSY)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: abort on (NO CARRIER)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: abort on (ERROR)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: report (CONNECT)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: timeout set to 10 seconds<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: send (AT&F^M)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: expect (OK)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: AT&F^M^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: OK<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: -- got it<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: send (ATE1^M)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: expect (OK)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: ^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: ATE1^M^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: OK<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: -- got it<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: send (AT+CGDCONT=1,"IP","ideagprs.com"^M)<5>Oct 13 10:28:30 Omega-7E32 kernel: [ 105.481113] random: crng init done<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: timeout set to 30 seconds<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: expect (OK)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: ^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: AT+CGDCONT=1,"IP","ideagprs.com"^M^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: OK<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: -- got it<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: send (ATD991#^M)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: expect (CONNECT)<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: ^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: ATD991#^M^M<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: CONNECT<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: -- got it<150>Oct 13 10:28:30 Omega-7E32 chat[2450]: send ( ^M)<30>Oct 13 10:28:30 Omega-7E32 pppd[2420]: Serial connection established.<6>Oct 13 10:28:30 Omega-7E32 kernel: [ 105.677834] 3g-hologram: renamed from ppp0<30>Oct 13 10:28:30 Omega-7E32 pppd[2420]: Using interface 3g-hologram<29>Oct 13 10:28:30 Omega-7E32 pppd[2420]: Connect: 3g-hologram <--> /dev/ttyUSB2<30>Oct 13 10:28:31 Omega-7E32 avahi-daemon[1826]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::42a3:6bff:fec1:7e33.<30>Oct 13 10:28:31 Omega-7E32 avahi-daemon[1826]: Joining mDNS multicast group on interface eth0.IPv6 with address fd1d:48c4:7633::1.<30>Oct 13 10:28:31 Omega-7E32 avahi-daemon[1826]: Registering new address record for fd1d:48c4:7633::1 on eth0..<30>Oct 13 10:28:31 Omega-7E32 avahi-daemon[1826]: Withdrawing address record for fe80::42a3:6bff:fec1:7e33 on eth0.<30>Oct 13 10:28:39 Omega-7E32 logread[1304]: Logread connected to 192.168.1.21:514<30>Oct 13 10:28:40 Omega-7E32 avahi-daemon[1825]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::42a3:6bff:fec1:7e33.<30>Oct 13 10:28:40 Omega-7E32 avahi-daemon[1825]: Joining mDNS multicast group on interface eth0.IPv6 with address fd1d:48c4:7633::1.<30>Oct 13 10:28:40 Omega-7E32 avahi-daemon[1825]: Registering new address record for fd1d:48c4:7633::1 on eth0..<30>Oct 13 10:28:40 Omega-7E32 avahi-daemon[1825]: Withdrawing address record for fe80::42a3:6bff:fec1:7e33 on eth0.<29>Oct 13 10:28:40 Omega-7E32 procd: /etc/rc.d/S96led: setting up led On<30>Oct 13 10:28:42 Omega-7E32 procd: - init complete -<27>Oct 13 10:28:42 Omega-7E32 uhttpd[2110]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:31:40 Omega-7E32 uhttpd[2119]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:31:45 Omega-7E32 uhttpd[2120]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:31:50 Omega-7E32 uhttpd[2121]: Error: Invalid directory /www: No such file or directory

    UDP socket deleted
    UDP socket created
    <13>Oct 13 10:35:20 Omega-7E32 root: [] Startup<13>Oct 13 10:35:21 Omega-7E32 root: /usr/bin/connectd_start_all started:<14>Oct 13 10:35:21 Omega-7E32 Connectd[2208]: Connectd Target built May 8 2020 at 23:29:53<14>Oct 13 10:35:21 Omega-7E32 Connectd[2208]: Version 4.9.1588980593 - (c)2019 remot3.it, Inc. All Rights Reserved<14>Oct 13 10:35:21 Omega-7E32 Connectd[2208]: Starting up as daemon<14>Oct 13 10:35:21 Omega-7E32 Connectd[2208]: Parent Exited Normally.<14>Oct 13 10:35:21 Omega-7E32 Connectd[2209]: Begin Startup.<14>Oct 13 10:35:21 Omega-7E32 Connectd[2211]: Creating pidfile /var/run/Connectdrmt365535.pid with PID 2211<14>Oct 13 10:35:21 Omega-7E32 Connectd[2211]: Using device uid = 80:00:00:00:01:07:9a:56<14>Oct 13 10:35:21 Omega-7E32 Connectd[2211]: initialize TCP target 127.0.0.1 port 65535<14>Oct 13 10:35:21 Omega-7E32 Connectd[2211]: 06066> Remot3it Registration Code Provided (checkhash 17:e7)<14>Oct 13 10:35:21 Omega-7E32 Connectd[2227]: Connectd Target built May 8 2020 at 23:29:53<14>Oct 13 10:35:21 Omega-7E32 Connectd[2227]: Version 4.9.1588980593 - (c)2019 remot3.it, Inc. All Rights Reserved<14>Oct 13 10:35:21 Omega-7E32 Connectd[2227]: Starting up as daemon<14>Oct 13 10:35:21 Omega-7E32 Connectd[2227]: Parent Exited Normally.<14>Oct 13 10:35:21 Omega-7E32 Connectd[2228]: Begin Startup.<14>Oct 13 10:35:21 Omega-7E32 Connectd[2230]: Creating pidfile /var/run/Connectdssh22.pid with PID 2230<14>Oct 13 10:35:21 Omega-7E32 Connectd[2230]: Using device uid = 80:00:00:00:01:07:fc:6b<14>Oct 13 10:35:21 Omega-7E32 Connectd[2230]: initialize TCP target 127.0.0.1 port 22<14>Oct 13 10:35:21 Omega-7E32 Connectd[2230]: 06066> Remot3it Registration Code Provided (checkhash 88:ea)<14>Oct 13 10:35:22 Omega-7E32 Connectd[2211]: 06076> sending req auth to 69.64.90.20:5959<14>Oct 13 10:35:22 Omega-7E32 Connectd[2230]: 06076> sending req auth to 69.64.90.20:5959<14>Oct 13 10:35:23 Omega-7E32 Connectd[2211]: 06078> Status redirect to 52.43.176.61:5961<14>Oct 13 10:35:23 Omega-7E32 Connectd[2211]: 06078> sending req auth to 52.43.176.61:5961<14>Oct 13 10:35:23 Omega-7E32 Connectd[2230]: 06079> Status redirect to 52.43.176.61:5963<14>Oct 13 10:35:23 Omega-7E32 Connectd[2230]: 06079> sending req auth to 52.43.176.61:5963<14>Oct 13 10:35:26 Omega-7E32 Connectd[2211]: 06116> sending req auth to 52.43.176.61:5961<14>Oct 13 10:35:26 Omega-7E32 Connectd[2230]: 06117> sending req auth to 52.43.176.61:5963<14>Oct 13 10:35:27 Omega-7E32 Connectd[2211]: 06119> NAT type selected at 3 with natmap 2<14>Oct 13 10:35:27 Omega-7E32 Connectd[2211]: Server Connection changed to state 4<14>Oct 13 10:35:27 Omega-7E32 Connectd[2230]: 06119> NAT type selected at 3 with natmap 2<14>Oct 13 10:35:27 Omega-7E32 Connectd[2230]: Server Connection changed to state 4<14>Oct 13 10:35:27 Omega-7E32 Connectd[2211]: Server Connection changed to state 5<14>Oct 13 10:35:27 Omega-7E32 Connectd[2211]: Connected to server is 52.43.176.61:5961

    UDP socket deleted
    UDP socket created
    <30>Oct 13 10:53:22 Omega-7E32 logread[1312]: Logread connected to 192.168.1.21:514<86>Oct 13 10:53:22 Omega-7E32 dropbear[2024]: Child connection from 192.168.1.21:59979<29>Oct 13 10:53:25 Omega-7E32 procd: /etc/rc.d/S96led: setting up led On<30>Oct 13 10:53:26 Omega-7E32 procd: - init complete -<27>Oct 13 10:53:27 Omega-7E32 uhttpd[2111]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:56:01 Omega-7E32 uhttpd[2120]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:56:06 Omega-7E32 uhttpd[2121]: Error: Invalid directory /www: No such file or directory<27>Oct 13 10:56:11 Omega-7E32 uhttpd[2122]: Error: Invalid directory /www: No such file or directory<30>Oct 13 10:56:11 Omega-7E32 procd: Instance uhttpd::instance1 s in a crash loop 6 crashes, 0 seconds since last crash<85>Oct 13 10:56:14 Omega-7E32 dropbear[2024]: Password auth succeeded for 'root' from 192.168.1.21:59979<5>Oct 13 10:56:58 Omega-7E32 kernel: [ 107.808260] random: crng init done<29>Oct 13 10:58:19 Omega-7E32 netifd: Interface 'loopback' is now down<29>Oct 13 10:58:19 Omega-7E32 netifd: Interface 'loopback' is disabled<29>Oct 13 10:58:19 Omega-7E32 netifd: Network device 'lo' link is down<29>Oct 13 10:58:19 Omega-7E32 netifd: Interface 'loopback' has link connectivity loss<29>Oct 13 10:58:19 Omega-7E32 netifd: wan (1868): udhcpc: received SIGTERM<30>Oct 13 10:58:26 Omega-7E32 logread[1312]: Logread connected to 192.168.1.21:514<150>Oct 13 10:58:27 Omega-7E32 chat[2388]: abort on (BUSY)<150>Oct 13 10:58:27 Omega-7E32 chat[2388]: abort on (NO CARRIER)<150>Oct 13 10:58:27 Omega-7E32 chat[2388]: abort on (ERROR)<150>Oct 13 10:58:27 Omega-7E32 chat[2388]: report (CONNECT)<150>Oct 13 10:58:27 Omega-7E32 chat[2388]: timeout set to 30 seconds

    0
  • C

    @Nagarjuna-Reddy I don't see anything obvious in the logs you have provided so my approach would be to simplify your device in order to assist in identifying the specific cause. The issue may be hardware, possibly a faulty board or faulty design, but at least we can look at the software first since that is easier to resolve.

    It seems your uhttpd is failing to start so if you don't need it then disable it. service uhttpd disable

    Next I would disable collectd and remote.it and see if that improves your reliability, I don't think remote.it technically supports OpenWrt.

    0 N 1 Reply
  • N

    @crispyoz
    Hi sir, remote.it it's needed for me remotely connectivity. I have created procd script for the remote.it backgrounds running. Earlier i have a running remote.it services in /etc/init.d/procd file. when the internet not happening reboot command is not working. that's why that script i am running in crontab every 5 mins. if service started already it will give the same message again and again. after i removed this script in /etc/init.d/procd file now reboot command is working.
    finally, my remote connection also working.

    uhttpd this for ports checking and web connectivity purpose we are using right. if i disable uhhtpd it won't any make the problem of my remote connectivity?.

    hardware issue means SIM should not detect right? but in this case SIM is detecting and signal also coming.
    when i am not running 3g.hologram (it's library for creating a PPP communication) my onion omega, not struct&hanging. only when i am running PPP script then only it's happening.
    some of the times when the internet has not happened i tried /etc/init.d/network restart.
    same scenario without SIM it's not making any problem. Only the problem is coming when i connected SIM then only.
    Hardware problem means 4G also should not work but here it's working.
    My GSM modem is working properly only in this condition, only Omega went down(hanging).

    0
  • C

    @Nagarjuna-Reddy I understand that you may need to run remote.it, but if that is the core problem causing your device to hang ("struct") then at least you know the cause and can address that specifically. If remote.it is messing up your system so that you can't even run reboot than that's not right.

    0 N 1 Reply
  • N

    @crispyoz
    Sir, I need your answer to what should i do?

    finally that 2G place i am going for 4G SIM.
    This struct & hanging it's happening some of the times also but rarely.
    At least can we solve these issues using watchdog timer?.
    Or can i make it watchdog timer as every 1 hour. if everything is fine then i will reset the watchdog timer to next hour like that way can i follow.

    0
  • C

    @Nagarjuna-Reddy watchdog timer is limited to 60 secs max, but if it runs every minute then it is also checking every hour. My previous comments regarding how to proceed remain the same.

    0 N 1 Reply
  • N

    @crispyoz I am running onion omega2s bord using 3.5V power supply and without power interrupt purpose i have connected 3.7V battery 2200 mah current. I used in between a Diode. Diode passing voltage as 3.5V. When i run firmware inside onion it has run a few days, after few days suddenly my onion omega has struct but voltage it's there in onion omega. So what could be the problem?.
    is there any way to check hardware issue? or software issue?

    0
  • C

    @Nagarjuna-Reddy Please create a new thread for this issue.

    0
  • N

    @crispyoz i am not able to get device logs. what i did wrong below?

    80218a11-eaaf-4bfd-ab76-53f1ad130c48-image.png

    0
  • C

    @Nagarjuna-Reddy use logread command then use grep to filter.

    0
project 26 onion omega2 15 omega setup 12 power outage 5
Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.