• Support

  • MoodleBox 4.6.0 is ultra slow

Hi Nicolas,
today is the first time that I can test the new MoodleBox 4.6.0.

The MoodleBox 4.6.0 is running on my Raspberry Pi 4B (4GB). It could ok a long time to connect to the Wifi. Now I could log in. The web server seems to be ultra slow. I changed the language and I purged the caches. Then I opened the MoodleBox dashboard. The cpu load is more than 6 … I think that this is too high.

The next thing I found is in the terminal. Is the name server running?

Last login: Fri Nov 10 19:36:15 2023 from 10.0.0.140
moodlebox@moodlebox:~ $ ping moodlebox.home
ping: moodlebox.home: Temporary failure in name resolution
moodlebox@moodlebox:~ $ sudo nano /etc/hosts

Yes, the hosts file opened but it took 2 minutes until I could see ir. Yes, the last line is correct

10.0.0.1   moodlebox

What should I do? What could be the problem?

Ralf

    ralfkrause The cpu load is more than 6 … I think that this is too high.

    You're right, this is way too long and abnormal, but I'm unable to reproduce.

    ralfkrause What should I do? What could be the problem?

    No idea. Did you try to reflash the image? Maybe try another SDcard. Is this reproducible with another device?

          Nicolas Did you try to reflash the image?

          Hi Nicolas,
          yes, I reflashed the microSD card with the same result yesterday. Now I took a new microSD card and I have no problems with my Raspberry Pi 4B (4GB RAM). Thank you for your fast answer so I am able to do more tests with the MoodleBox this microSD card.

          The cpu load is 0.099, 0.23, 0.175 now. I think that these are the normal values.

          How long will I see your home computer in my MoodleBox? 10.0.0.213 (iMac-bureau) :-)
          You can see it on the image in the first post of this thread.

          Best regards,
          Ralf

              ralfkrause How long will I see your home computer in my MoodleBox? 10.0.0.213 (iMac-bureau) :-)

              Gosh, I forgot to put it away before to cut the image.

              It should normally go away automatically, but you can simply delete the file /tmp/dnsmasq.leases and it will disappear.