something went wrong with my Raspberry/Jessie!
The WU's will crunching well in about 11-12h.
But...
1. I'm to stupid to set the Pi to a static IP. Whenever I set a static IP after reboot I get dhcp as well.
2. The Monitor going to sleep an mostly doesn't come back
3. After a few hours the system is frozen and sometimes I'm able to see a dump on the screen (somewhat scheduler or so)
4. raspi-config ignore my setting to come up only with consolescreen no GUI is wanted by me, because I've to learn/understand managing Unix by Console! :-)
Temp is fine with active cooling less than 70°! atm 54,1!° yesterday 64,1° max by about 28-30° Temp outdoor!
Are there any Logs wich I (we ;-)) can have a look of to post here and find out what is going/configured wrong?
I only want to use this System for crunching, perhaps there are Packages which could be removed and are the Reasons of the Faults.
after 14h the System is halted again with no error on the screen.
So far 4 Units finished in about 50.000 sec.
For plotting and searching the reason of the behavior from this pi I installed RPI-Monitor and noticed that the free Memory is going to zero over a time of 14h. At the End, the free Memory falls from at least 103 MB to zero. That's the time where the Pi is stopping. Running WU's at this point didn't crash.
Any suggestion where I should start searching for this Error?
Any suggestion where I should start searching for this Error?
THX
Logging memory consumption of processes might give some insights.
E.g. you could instruct the Pi to log the output of top once per hour to a file, you should then be able to identify the process(es) that cause this, e.g.
Logging memory consumption of processes might give some insights.
E.g. you could instruct the Pi to log the output of top once per hour to a file, you should then be able to identify the process(es) that cause this, e.g.
Well, at least this seems make it less likely that there is something on the PI which slowly eats up all the memory (at least not on the timescale of hours.
You could make the logging of top finer (say, once every minute) but I rather suspect it's something different.
The power supply is ok? The red LED should be always on, if it's flickering, this indicates a "brown-out" => PSU cannot supply a stable voltage
Does this happen also when you are not overclocking?
Well, at least this seems make it less likely that there is something on the PI which slowly eats up all the memory (at least not on the timescale of hours.
You could make the logging of top finer (say, once every minute) but I rather suspect it's something different.
The power supply is ok? The red LED should be always on, if it's flickering, this indicates a "brown-out" => PSU cannot supply a stable voltage
Does this happen also when you are not overclocking?
I would copy that it didn't make sense to logging every minute.
I've noticed, that the event of Memory break down is near same time my Fritbox will be disconnected from the Internet (every morning between 3-4am).
At this Event I will loss 120 MB in one Moment.
Because the power supply I can't see any flickering at any time, so I've to assume that the Power is stable.
Early up this morning I've shut off overclocking completely and will have a look if there is any change in the behavior.
But I also think that something is wrong until I didn't resolve the other Problems like:
- didn't get an IP every boot from fritzbox DHCP (ever the same IP) over LAN
- can't set static IP
- can't switch off the screensaver
- can't prevent the System of starting the GUI
Any suggestions?
Otherwise I will set up the Pi with another SD Card from scratch with wheezy and without jessie, but the named Problems persist even before I've upgraded to jessie (very frustrating)!
...temperature is not the problem!
2 Days quite less than 60 Grad Celsius.
I've changed the Pi from overclocking pi2 to normal and the only which is changing, is the time until the free memory is going down. So the Pi will longer stay up.
Pi2's are very particular about the power supplied. try another power supply and make sure that it meets/supplies clean power. Some Pi2 users have used power supplies from earlier models and have had problems using them on a Pi2.
One other consideration might be the class of the SD card. I have always used Class 10 rated cards. I have seen where some are recommending class 6 or better.
As a new RasPi2+Raspbian owner, may I ask why you compile boinc by yourself instead of using the one from the distribution?
Or you could use the Jessie release and get 7.4.23 from the repo.
One has to be careful, tho: Not all the software in Raspbian wheezy is already in Raspbian Jessie, e.g. I got some stuff from Jessie (I think the main thing was gnuradio) which in the end made Mathematica unusable because of dependency conflicts.
Cheers
HB
Ubuntu Mate is Ubuntu's offering for the Pi2. It must be installed on a Pi2 - not backwards compatible with earlier models. Ubuntu's repository supplies boinc 7.2.42+dfsg. I am running Mate on two Pi2 now but I am not using them to crunch data.
Hi Folks, something went
)
Hi Folks,
something went wrong with my Raspberry/Jessie!
The WU's will crunching well in about 11-12h.
But...
1. I'm to stupid to set the Pi to a static IP. Whenever I set a static IP after reboot I get dhcp as well.
2. The Monitor going to sleep an mostly doesn't come back
3. After a few hours the system is frozen and sometimes I'm able to see a dump on the screen (somewhat scheduler or so)
4. raspi-config ignore my setting to come up only with consolescreen no GUI is wanted by me, because I've to learn/understand managing Unix by Console! :-)
Temp is fine with active cooling less than 70°! atm 54,1!° yesterday 64,1° max by about 28-30° Temp outdoor!
Are there any Logs wich I (we ;-)) can have a look of to post here and find out what is going/configured wrong?
I only want to use this System for crunching, perhaps there are Packages which could be removed and are the Reasons of the Faults.
THX
Greetings from the North
Hi, after 14h the System
)
Hi,
after 14h the System is halted again with no error on the screen.
So far 4 Units finished in about 50.000 sec.
For plotting and searching the reason of the behavior from this pi I installed RPI-Monitor and noticed that the free Memory is going to zero over a time of 14h. At the End, the free Memory falls from at least 103 MB to zero. That's the time where the Pi is stopping. Running WU's at this point didn't crash.
Any suggestion where I should start searching for this Error?
THX
Greetings from the North
RE: Any suggestion where
)
Logging memory consumption of processes might give some insights.
E.g. you could instruct the Pi to log the output of top once per hour to a file, you should then be able to identify the process(es) that cause this, e.g.
do
crontab -e
to edit the crontab file, and then add a line
0 * * * * top -n 1 -b >> /home/pi/top_history.log
HB
RE: Logging memory
)
I've do so, the Log can be read there:
https://www.dropbox.com/s/3c6icrdmnwwqntd/top_history.log?dl=0
But I can't see nothing unusual.
So far, sunny WE
THX
Greetings from the North
Well, at least this seems
)
Well, at least this seems make it less likely that there is something on the PI which slowly eats up all the memory (at least not on the timescale of hours.
You could make the logging of top finer (say, once every minute) but I rather suspect it's something different.
The power supply is ok? The red LED should be always on, if it's flickering, this indicates a "brown-out" => PSU cannot supply a stable voltage
Does this happen also when you are not overclocking?
Cheers
hb
RE: Well, at least this
)
I would copy that it didn't make sense to logging every minute.
I've noticed, that the event of Memory break down is near same time my Fritbox will be disconnected from the Internet (every morning between 3-4am).
At this Event I will loss 120 MB in one Moment.
Because the power supply I can't see any flickering at any time, so I've to assume that the Power is stable.
Early up this morning I've shut off overclocking completely and will have a look if there is any change in the behavior.
But I also think that something is wrong until I didn't resolve the other Problems like:
- didn't get an IP every boot from fritzbox DHCP (ever the same IP) over LAN
- can't set static IP
- can't switch off the screensaver
- can't prevent the System of starting the GUI
Any suggestions?
Otherwise I will set up the Pi with another SD Card from scratch with wheezy and without jessie, but the named Problems persist even before I've upgraded to jessie (very frustrating)!
THX a lot to yours
Greetings from the North
I had intermittent lock-ups
)
I had intermittent lock-ups about once a week from my overclocked Pi2's. I set them back to stock and I haven't had a lock-up for a few weeks now.
I have copper heatsinks on the SoC and no top of the case so they shouldn't be overheating, besides its winter down here at the moment.
BOINC blog
...temperature is not the
)
...temperature is not the problem!
2 Days quite less than 60 Grad Celsius.
I've changed the Pi from overclocking pi2 to normal and the only which is changing, is the time until the free memory is going down. So the Pi will longer stay up.
Very frustrating.
THX
Greetings from the North
Pi2's are very particular
)
Pi2's are very particular about the power supplied. try another power supply and make sure that it meets/supplies clean power. Some Pi2 users have used power supplies from earlier models and have had problems using them on a Pi2.
One other consideration might be the class of the SD card. I have always used Class 10 rated cards. I have seen where some are recommending class 6 or better.
RE: RE: RE: As a new
)
Ubuntu Mate is Ubuntu's offering for the Pi2. It must be installed on a Pi2 - not backwards compatible with earlier models. Ubuntu's repository supplies boinc 7.2.42+dfsg. I am running Mate on two Pi2 now but I am not using them to crunch data.