×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Re:Unexpected shut down of KStars and Ekos, but not Indi server

  • Posts: 90
  • Thank you received: 12
I have the same problem running on pi3. I thought it was a memory problem but it happens still after I added 3Gb swap.
And the problem appears to happen more frequently when it's connected to the mount.
4 years 5 months ago #44066

Please Log in or Create an account to join the conversation.

  • Posts: 9
  • Thank you received: 0
I also have that problema, using Stellarmate on a Raspberry pi 3b+.

While guiding and imaging, suddenly Kstars disappears but PHD2 continues guiding and Indi seems to remain connected.
After i restart Kstars and connect, a pop up window tells me that there is already an instance of Indi running. I chose to stop it and then Kstars can start workng again.

Greetings.
4 years 5 months ago #44156

Please Log in or Create an account to join the conversation.

  • Posts: 1119
  • Thank you received: 182
Looks to me this is a Raspberry Pi problem. It does not happen (or only very rarely) when I am running KStars on my Zotac mini-PC.
May be it running out of memory. I added 4 GB swap and that seems to have helped.
4 years 5 months ago #44170

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Yeah, If it happens on Raspberry PI and not on another computer, it probably is a memory issue. But if you can reliably produce a crash on different systems, we should see why it does crash.

NOTE: I wouldn't recommend a SWAP file on a raspberry pi due to issues with reading and writing of the SD card. You will wear it out. There is something much better called zram. Basically it takes the system ram, makes a compressed swap file for it, and puts the swap file in RAM instead of on the system disk. There is a slight performance hit since the system now has to do access compressed ram on a swap file in memory instead of just accessing memory. But the performance hit is worth the system not crashing. And it is also better than wearing out your SD card.
4 years 5 months ago #44173

Please Log in or Create an account to join the conversation.

  • Posts: 1119
  • Thank you received: 182
Hi Rob,

I can't "reliably" induce a crash of KStars, it seems to happen randomly to me, at least. The Zotac mini-PC I am using also has just 4 GB of RAM, but my Swap file there resides on the eMMC, not an SD card.
With respect to wearing out the SD card, I am less concerned about that. First, I had a swap file on my Pi3 and that was used extensively over the last year without any problem. The Swap file on the Pi4 so far appears to be used very sparingly (swappiness set at 20) and I put it only as a safeguard in case memory gets tight. Second, I don't know how to turn on zRAM in Ubuntu MATE on the Pi4. What is the procedure to do that? Third, microSD cards are really cheap now (I am using a 128 GB card from Samsung that costs $20 and it already last for over a year).
I actually ran my Pi4 without a hitch through the night 2 nights ago, but I did not use guiding. I have the suspicion that handing two cameras and other intensive tasks might be the problem. One of the crashes I had earlier occurred right during the meridian flip.
4 years 5 months ago #44174

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
For Ubuntu MATE:

sudo apt -y install zram-config

It takes care of everything. If you currently have 4 GB of ram, this will give you close to 8 GB
The following user(s) said Thank You: Jose Corazon
4 years 5 months ago #44177

Please Log in or Create an account to join the conversation.

  • Posts: 77
  • Thank you received: 1
Last night I tried my first session with my RP4 2gb running KStars on Raspbian.
Polar alignment ran perfectly and smooth (also in full screen).
Guiding ran so I started a small imaging session of 1x60s, 1x120, 1x180, 1x240 and 1x300s subs. During the 180 sub, I wanted to check the Stars on the 120 s and my messing about with the fits viewer, while guiding and taking a 180s sub, caused KStars to crash.
After restarting and reconnecting etc I tried the same imaging session again, this time leasing the poor fits viewer alone. This time no crash.
I then slewed to a New target, solved and synced and started a one hour session of 30s subs - no problems. Darks, Bias and flats afterwards without problems.
So I’ll just try not to push my 2GB RP4 too hard :-) I did notice that my cooler fan was running pretty much all the way through my session.
SkyWatcher ED80 Pro
Skywatcher HEQ5 Pro with Rowan Belt Mod with EQDIR cable
ZWO ASI294MC Pro imaging camera
QHY5L-II-C guide camera on 50mm guidescope
DeepSkyDad AF3 autofocuser
Raspberry Pi 4 4GB running Kstars/Ekos
4 years 5 months ago #44178

Please Log in or Create an account to join the conversation.

  • Posts: 321
  • Thank you received: 19
Just wanted to inform that i have crashes here too. Running KStars on my ASUS VIVOBOOK with KDE Neon and Plasma.
I can sometimes trigger that by using the fitsviewer, and sometimes its just out of nothing...
But when a session is running, and i do not do too much clicking around its stable.

cheers
Niki
Skywatcher EQ6-R | Lacerta 10" Carbon-Newton | Lacerta MFoc Motorfocus | Moravian G2 8300 Color | Canon EOS 5DMarkIIIa | Lodestar X2 guiding cam | KSTARS 3.4.3. on my outdoor-Laptop with KDE-Neon/Plasma | KSTARS 3.4.3. on Remote-IMac with Catalina | KSTARS 3.4.3 on Remote-Macbook Air with Catalina
4 years 5 months ago #44179

Please Log in or Create an account to join the conversation.

  • Posts: 83
  • Thank you received: 6

Same here. I don't remember crashing in another module, but most of the time if I play with the fits viewer, trying to zoom or touching the "default zoom" or anything related I crash 8 times out of 10. Very frustrating, so I try to do without using the zoom feature at all.
"Some people are so poor, all they have is money"
SW Black Diamond 80ED | SW150MAK | Newton SW 200/1000 | Orion 50mm Guider with Helical Focuser |Sirius EQ-G Rowan Belt Mode
Canon 1000D moded | ZWO ASI185MC | Baader Mark III Zoom
INDI | Stellarmate on RPI3B+ | Stellarium | Pixinsight
Last edit: 4 years 5 months ago by Yannic Delisle.
4 years 5 months ago #44180

Please Log in or Create an account to join the conversation.

There was a fix to a crash in FITS Viewer in nightly builds a few days ago. So it would help to know if you're using nightly or stable. For the advanced users, a gdb backtrace would *immensely* helpful.
The following user(s) said Thank You: the.cakemaker
4 years 5 months ago #44188

Please Log in or Create an account to join the conversation.

  • Posts: 321
  • Thank you received: 19
Hey Jasem.

ATM i use the latest stable version.
I‘ll have a try on latest nightly.

I will habe to write down how to install...
Too less linux-knowledge, used too less times...

Cheers
Niki


Gesendet von iPhone mit Tapatalk
Skywatcher EQ6-R | Lacerta 10" Carbon-Newton | Lacerta MFoc Motorfocus | Moravian G2 8300 Color | Canon EOS 5DMarkIIIa | Lodestar X2 guiding cam | KSTARS 3.4.3. on my outdoor-Laptop with KDE-Neon/Plasma | KSTARS 3.4.3. on Remote-IMac with Catalina | KSTARS 3.4.3 on Remote-Macbook Air with Catalina
4 years 5 months ago #44189

Please Log in or Create an account to join the conversation.

  • Posts: 326
  • Thank you received: 50
Last night I had a successful session with my usual setup having switched back to my Canon 450D. At first I tried my 550D, but on each of two times I tried to Polar Align, KStars/Ekos would crash just before showing the Alignment Frame I.e. at the end of the 3 plate solves. Back with the 450D and no crashes. I noted a significant difference in the solving times between the two cameras 9 secs for the 12Mpixel 450D, twice as long for the 18Mpixel 550D. Next clear night I’ll try out my RPi4 4GB rather than my 2GB, although the latter is housed in a flirc case and stays very cool outside with no fan.
4 years 5 months ago #44408

Please Log in or Create an account to join the conversation.

Time to create page: 0.559 seconds