Antsle Forum

Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more. 

Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked. 

Please or Register to create posts and topics.

Antsle just started crashing, Now won't boot

akak01000101@akak01000101
67 Posts
#1 · October 4, 2022, 3:08 pm
My antsle crashed 3 times in the last 2 days. Two times during the night when no jobs or anything was running, and the 3rd time just now when I started antlets that didn't automatically start up. Below are various logs collected, but nothing really recorded when it crashed accept a bunch of ^@^@^@.
Any help is greatly appreciated.

edgeLinux version (formerly antsleOS) 0.12.1

antMan 3.4.3 License: Proprietary antMan license.
kern.log is showing:
Oct  4 09:18:24 myantsle kernel: [   37.855953] virbr1: topology change detected, propagating
Oct  4 09:18:24 myantsle kernel: [   38.238953] virbr1: port 5(vnet4) entered forwarding state
Oct  4 09:18:24 myantsle kernel: [   38.238956] virbr1: topology change detected, propagating
Oct  4 09:18:24 myantsle kernel: [   38.622942] virbr1: port 6(vnet5) entered forwarding state
Oct  4 09:18:24 myantsle kernel: [   38.622945] virbr1: topology change detected, propagating
Oct  4 09:32:19 myantsle kernel: [  873.237560] virbr1: port 7(vnet7) entered blocking state
Oct  4 09:32:19 myantsle kernel: [  873.237563] virbr1: port 7(vnet7) entered disabled state
Oct  4 09:32:19 myantsle kernel: [  873.237645] device vnet7 entered promiscuous mode
Oct  4 09:32:19 myantsle kernel: [  873.237874] virbr1: port 7(vnet7) entered blocking state
Oct  4 09:32:19 myantsle kernel: [  873.237876] virbr1: port 7(vnet7) entered listening state
Oct  4 09:32:19 myantsle kernel: <30>[  873.238963] systemd-udevd[3386]: link_config: autonegotiation is unset or enabled, the speed and duplex are
daemon.log is showing:
Oct  4 09:18:45 myantsle dnsmasq-dhcp[6588]: DHCPREQUEST(virbr1) 10.1.1.12 b2:61:6e:73:6c:0c
Oct  4 09:18:45 myantsle dnsmasq-dhcp[6588]: DHCPACK(virbr1) 10.1.1.12 b2:61:6e:73:6c:0c antlet12
Oct  4 09:18:47 myantsle dnsmasq-dhcp[6588]: DHCPREQUEST(virbr1) 10.1.1.10 b2:61:6e:73:6c:0a
Oct  4 09:18:47 myantsle dnsmasq-dhcp[6588]: DHCPACK(virbr1) 10.1.1.10 b2:61:6e:73:6c:0a antlet10
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
Oct  4 09:34:01 myantsle ntpd[6879]: ntpd 4.2.8p13@1.3847-o Wed Apr 10 08:05:00 UTC 2019 (1): Starting
Oct  4 09:34:01 myantsle ntpd[6879]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g
syslog Logs are just showing 
Oct  4 09:32:29 myantsle kernel: <28>[  882.726061] systemd-udevd[5122]: Process 'net.sh vnet9 start' failed with exit code 1.
Oct  4 09:32:29 myantsle kernel: [  882.810765] virbr1: port 8(vnet8) entered forwarding state
Oct  4 09:32:29 myantsle kernel: [  882.810767] virbr1: topology change detected, propagating
Oct  4 09:32:31 myantsle kernel: [  884.730737] virbr1: port 9(vnet9) entered learning state
Oct  4 09:32:32 myantsle ntpd[6328]: Listen normally on 18 vnet9 [fe80::fc61:6eff:fe73:6c32%26]:123
Oct  4 09:32:33 myantsle kernel: [  886.778757] virbr1: port 9(vnet9) entered forwarding state
Oct  4 09:32:33 myantsle kernel: [  886.778759] virbr1: topology change detected, propagating
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^^@^@^@^@^@^@^@^@^@^@^@^@^@^@Oct  4 09:33:59 myantsle syslogd 1.5.1: restart.
Oct  4 09:34:00 myantsle kernel: klogd 1.5.1, log source = /proc/kmsg started.
Oct  4 09:34:00 myantsle kernel: Inspecting /boot/System.map-4.14.83-gentoo
Oct  4 09:34:01 myantsle kernel: Inspecting /usr/src/linux/System.map
Oct  4 09:34:01 myantsle dhcpcd[6504]: br0: no IPv6 Routers available
# vi antman.log
2022-10-04 08:29:46,489 INFO  antman.env -
-=[antman started successfully]=-
2022-10-04 08:30:03,793 INFO  luminus.http-server - starting HTTP server on port 3000
2022-10-04 08:30:03,827 INFO  antman.core - #'antman.config/env started
2022-10-04 08:30:03,827 INFO  antman.core - #'antman.handler/init-app started
2022-10-04 08:30:03,828 INFO  antman.core - #'antman.core/http-server started
2022-10-04 08:30:03,828 INFO  antman.core - #'antman.core/repl-server started
2022-10-04 09:18:57,482 INFO  antman.env -
-=[antman started successfully]=-
2022-10-04 09:19:14,432 INFO  luminus.http-server - starting HTTP server on port 3000
2022-10-04 09:19:14,466 INFO  antman.core - #'antman.config/env started
2022-10-04 09:19:14,466 INFO  antman.core - #'antman.handler/init-app started
2022-10-04 09:19:14,466 INFO  antman.core - #'antman.core/http-server started
2022-10-04 09:19:14,466 INFO  antman.core - #'antman.core/repl-server started
2022-10-04 09:34:39,223 INFO  antman.env -
-=[antman started successfully]=-
2022-10-04 09:34:56,160 INFO  luminus.http-server - starting HTTP server on port 3000
2022-10-04 09:34:56,193 INFO  antman.core - #'antman.config/env started
2022-10-04 09:34:56,194 INFO  antman.core - #'antman.handler/init-app started
2022-10-04 09:34:56,194 INFO  antman.core - #'antman.core/http-server started
2022-10-04 09:34:56,194 INFO  antman.core - #'antman.core/repl-server started
Click for thumbs down.0Click for thumbs up.0
Last edited on October 5, 2022, 9:18 am by akak01000101
akak01000101@akak01000101
67 PostsTopic Author
#2 · October 5, 2022, 9:19 am

Just got worse! After a complete powercycle it will not boot. Everything starts booting fine until it gets to

*Mounting network filesystem....

*Checking nginx'  configurations....

*starting nginx ...

<short pause>

Then the system resets

Click for thumbs down.0Click for thumbs up.0
daniel.luck@daniel-luck
552 Posts
Antsle Staff
#3 · October 5, 2022, 6:12 pm

Hi Kirk:

Thanks for contacting antsle Support.

Thanks for providing the logs. Have you checked in this log: /var/log/messages?
It can take some time reviewing the logs to figure out what might have happened. Most times when the system crashes the logs are not written to. It could be a hardware issue maybe a heat issue

If you have your antlets backed up already, you can also try performing factory reset / fresh install of edgeLinux and antMan. This will get on our latest version of OS and antMan.
https://docs.antsle.com/get-started/getting-started-with-edgelinux-software-only-version

Thank you,
antsle Support

Click for thumbs down.0Click for thumbs up.0
Last edited on October 5, 2022, 6:12 pm by daniel.luck
akak01000101@akak01000101
67 PostsTopic Author
#4 · October 5, 2022, 6:16 pm

Its worse now... When it gets plugged in the button in the front does nothing, and the red blinking light in the front tends to blink is some kind of patterned or random pattern sequence. Something like....

blink,, blink,, blink blink blink

blink,, blink,, blink blink blink blink

blink,, blink,, blink,, blink-blink

Non-the-less, nothing is displayed on the monitor and it doesn't even get to Post. Wondering if power Supply is dying.

Click for thumbs down.0Click for thumbs up.0
daniel.luck@daniel-luck
552 Posts
Antsle Staff
#5 · October 10, 2022, 6:17 pm

HI @akak01000101

Yes, we would recommend changing out the Power Supply first.

Power Supply – Antsle one Series

Thanks,
antsle Support

Click for thumbs down.0Click for thumbs up.0
akak01000101@akak01000101
67 PostsTopic Author
#6 · October 14, 2022, 9:44 am

[SOLVED]

It was the power supply..... Whew!!!

Power Supply – Antsle one Series

Verify it works with your model first.

Click for thumbs down.0Click for thumbs up.2
lancem and daniel.luck have reacted to this post.
lancemdaniel.luck
daniel.luck@daniel-luck
552 Posts
Antsle Staff
#7 · October 17, 2022, 9:19 am

Hi @akak01000101

Thanks for the update.  Glad that worked for you.

Thank you,
antsle Support

Click for thumbs down.0Click for thumbs up.0