Skip to content

Loading…

Install problem #184

Closed
mappler opened this Issue · 8 comments

2 participants

@mappler

I had a little trouble installing the WebIDE. I'm not sure what I did wrong, so I'm posting as an issue. I'm using Raspbian "wheezy" as the OS. It should be the 2-9-2013 version. uname -a returns the following: Linux raspberrypi 3.6.11+ #371 PREEMPT Thu Feb 7 16:31:35 GMT 2013 armv6l GNU/Linux

I installed using the "Easy Installation" method, copying the commands with the "Copy Code" button into an SSH window. I received the confirmation messages. However, when I tried to connect to the device (using http://192.168.1.6), it did not respond.

I issued sudo service adafruit-webide.sh start
It claimed to be running.
I issued sudo service adafruit-webide.sh restart
It failed
I issued sudo service adafruit-webide.sh stop
then, start again.

Still no luck connecting.

I tried rebooting the pi.
No luck connecting.

I ran redis-cli
It claimed the redis-server was NOT running.
I ran redis-server, in the background. Now, everything worked.

I don't understand why redis-server didn't start without being manually run.

Thanks in advance for any help.

-Matt

@jwcooper
Adafruit Industries member

Thank you for the details report. I've seen this a couple of times now, where redis-server doesn't get installed as a daemon for some reason.

The only tips I can give are to manually set it up as a daemon, and setup an init.d script for it.

You could try using something like this:
https://gist.github.com/lsbardel/257298

Do you have a redis-server script in /etc/init.d already?

@mappler

Yes, the redis-server script is there in /etc/init.d. The symlinks are also in the /etc/rcx..d directories.
This message appears in /var/log/syslog seven times when I reboot:
Apr 5 16:07:49 raspberrypi restartd: webide is NOT running, executing 'service adafruit-webide.sh restart'

/var/log/redis has these messages:
[2270] 05 Apr 16:05:53 # Warning: 32 bit instance detected but no memory limit set. Setting 3.5 GB maxmemory limit with 'noeviction'
policy now.
[2270] 05 Apr 16:05:53 * Server started, Redis version 2.4.14
[2270] 05 Apr 16:05:53 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this iss
ue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to
take effect.
[2270] 05 Apr 16:05:53 # Short read or OOM loading DB. Unrecoverable error, aborting now.

@jwcooper
Adafruit Industries member

Thanks for the detailed logs...very useful.

How much free disk space do you have on your pi?

@mappler

I think that is it. Disk space was (mostly) full. I had never expanded the Wheezy image to the size of the SD card, so it was essentially out. I bet this is the issue. Even after resolving this and expanding the size of the disk, redis-server does not start on startup. However, I'm guessing something has gone wrong during initial installation that is preventing this? Anything else you want me to try before I try reinstalling the WebIDE with an appropriate amount of disk space?

@jwcooper
Adafruit Industries member

Yea, I'm guessing the redis db was corrupted due to the disk space issue.

Try uninstalling redis, and re-installing it. You may need to manually delete the dump.db file too.

@mappler

I uninstalled it. I also manually deleted the dump.db file. However, it will not seem to recreate it properly. redis-server starts up properly now on reboot. However, every time I connect it is like connecting for the first time. It seems it will not rewrite the database. Any thoughts?

Note: This is not a MAJOR issue for me. I happy to rewrite the SD card and start fresh. I'm also happy to work through these issues to help others. Thank you for your assistance.
-Matt

@jwcooper
Adafruit Industries member

Did redis create a new dump.rdb file?

It can take up to 15 minutes for the data to write out to the dump.rdb file, I'm not sure if it flushes on restart or not (I would assume it does though).

@mappler

Yep, that was it. Just took time for it to write out that file. Everything seems to be working fine now.
I'm almost positive that lack of disk space was the issue. Wheezy is pretty tight on disk space once you install a few things. Well, assuming you forget to expand the file system!! I don't think we had put on a wealth of software on it. We added WiringPi, and the libraries we needed to talk to I2C chips. I think we also added the GPIO components for Scratch. So, with a just a few libraries, we had filled up the / partition.

I believe you can mark this issue closed.

@mappler mappler closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.