I have installed Astrobox numerous times with 4 different micro sd cards and I’m still getting this problem.
During setup 10.10.0.1 works fine and I can set up Astrobox,but when I do a reboot and the Astrobox gets an IP address from my router,that’s when I get the “Your Astrobox is still booting up” screen. The only way to get it to come back up is by doing another install and then it does it again.
It’s on my network because I can SSH into the PI. Ideas? Thanks
How big is your microSD card? I wonder if your storage is running out.
The only time I experienced this problem, the microSD card was the problem. I used a new microSD card and it worked fine. Check your microSD card capacity before and after flashing just to be sure.
Also, I am assuming that when you click Reload Page in the Your Astrobox is still booting up screen, nothing happens?
I’m using a 32gb micro sd card.
Yes,after I keep hitting the reload page,nothing happens.
Looking at the file system it says I have 28.5 GB free.
Weird. Are you able to plug in the Astrobox to a monitor to see the boot up process? Perhaps it hangs somewhere with an error message? That might give us a clue into why it hangs during the boot up process.
It could be some driver/module not loading…
I have seen on other web interfaces that sometimes the browser cache gets messed up. Reload would you expect fix it but doesn’t. You might try clearing the browser cache then quiting and reopening browser then try hitting the astrobox fresh.
Just a thought.
FYI the logs are located at:
/var/log/astrobox/astrobox.log
If you could send them to us, it would be helpful. Please do so by creating a ticket in https://astroprint.zendesk.com
I’ll be hook to a monitor and see if anything shows. I’ll also clear the browser cache and send the log files.
Deleting cache didn’t work and I didn’t see any error when connected to a momitor.
Daniel,log files was sent.
Any luck on the log files I sent Daniel?
I am having this exact same issue.
Page says “AstroBox is booting up.”, never goes away.
The Pi (3) is up and running and I can SSH into it just fine (aka it is booted).
@Kev7274 did you ever figure this out?
When you reimage makes sure you use sdcardformatter or similar to format the sd card back to a fresh slate. Just reimaging the sd card only caused all sorts of issues for me, you can tell it does something different because if you reimage only it takes seconds, if you properly format the sd card then re image it takes minutes and rebuilds the image from start to finish. I don’t know exactly what goes on but that’s what i’ve found from my little experiment and i’ve had no more issues since…touch wood!
When you ssh into the Pi csn you tell if the Astrobox application is tunning via ‘ps’ command?
Also looking at the /var/log/astrobox/astrobox.log might shed some light into why the astrobox service is having problems starting or it s taking so long
Here are the processes running:
pi@astrobox-3890:/AstroBox $ ps axuw | grep astrobox
root 374 0.0 0.1 1912 1172 ? Ss 14:24 0:00 /bin/sh /etc/init.d/astrobox start
avahi 392 0.0 0.2 3876 2456 ? Ss 14:24 0:00 avahi-daemon: running [astrobox-3890.local]
root 871 0.0 0.0 1912 388 ? S 14:25 0:00 /bin/sh /usr/local/sbin/astrobox-init
pi 1104 0.0 0.2 4280 1876 pts/0 S+ 14:29 0:00 grep --color=auto astrobox
The log file doesn’t seem to exist:
pi@astrobox-3890:/AstroBox $ more /var/log/astrobox/astrobox.log
/var/log/astrobox/astrobox.log: No such file or directory
It almost seems like astrobox is never actually finishing it’s init? I have tried reformatting the SD and re-imaging as well as swapping out for another SD.
I am sure you have tried this, but have attempted to boot with no usb devices (including the printer) plugged in?
Also maybe try with just the network cable since this is a pi3 maybe it has something to do with the wireless and I think having the hard line ethernet installed will perhaps cause it to ignore the wifi…Daniel will know better.
I agree it seems like the astrobox is not completing the boot…since it is a fresh image really it seems like a ‘hardware’ issue…there are some other logs you can look at but I will have to get back to you on which ones…maybe boot with a monitor attached and see if you see anything odd during the boot.
So I have tried multiple Pis (a 2 and a 3), the only thing connected is the Ethernet and power (LulzBot Mini disconnected).
The Pi does boot. I can SSH into it and all is well. A dmesg doesn’t reveal anything strange or out of order.
I am sure there is something dead simple I am missing but for the life of me I can’t figure it out. On this same hardware I did install Octoprint (via the same process I flash for Astroprint) and it seems to work fine.
I just looked at my astrobox using ‘ps’
I wonder if you try this:
cat /var/run/astrobox.pid
and
service astrobox status
and maybe:
service astrobox restart
I have found when writing my own network based service routines on the pi, odd things happen when the network is not up when the service thinks it is…I looked at the astrobox service handler and it uses a slightly different mechanism for determining the network status than I do (basically it pings the google dns) but that assumes the hardware is already up and connected…which it should be but sometimes not.
There is no pid:
root@astrobox-1543:/var/run# cat /var/run/astrobox.pid
cat: /var/run/astrobox.pid: No such file or directory
Yet the service seems to be loaded…
root@astrobox-1543:/var/run# service astrobox status
● astrobox.service - LSB: AstroBox
Loaded: loaded (/etc/init.d/astrobox)
Active: activating (start) since Wed 2016-07-13 14:29:44 UTC; 53s ago
Control: 378 (astrobox)
CGroup: /system.slice/astrobox.service
├─378 /bin/sh /etc/init.d/astrobox start
├─891 /bin/sh /usr/local/sbin/astrobox-init
└─909 ntpd -gq
Jul 13 14:29:55 astrobox-1543 ntpd[909]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jul 13 14:29:56 astrobox-1543 ntpd[909]: Listen and drop on 1 v6wildcard :: UDP 123
Jul 13 14:29:56 astrobox-1543 ntpd[909]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jul 13 14:29:56 astrobox-1543 ntpd[909]: Listen normally on 3 eth0 10.51.1.227 UDP 123
Jul 13 14:29:56 astrobox-1543 ntpd[909]: Listen normally on 4 lo ::1 UDP 123
Jul 13 14:29:56 astrobox-1543 ntpd[909]: Listen normally on 5 eth0 fe80::2597:a283:21de:338d UDP 123
Jul 13 14:29:56 astrobox-1543 ntpd[909]: peers refreshed
Jul 13 14:29:56 astrobox-1543 ntpd[909]: Listening on routing socket on fd #22 for interface updates
Jul 13 14:29:58 astrobox-1543 ntpd[909]: Listen normally on 6 eth0 10.51.1.226 UDP 123
Jul 13 14:29:58 astrobox-1543 ntpd[909]: peers refreshed
But when I tell the service to restart… it gets a pid:
root@astrobox-1543:/var/run# service astrobox restart
root@astrobox-1543:/var/run# cat /var/run/astrobox.pid
1115
It appears I need to restart it after every boot… not sure why. But at least I can get in and start playing with it. 
edit: a letter
Oh and thank you for all your help getting me this far.