- This topic is empty.
August 7, 2014 at 10:16 am #23096
I have Python Interval Program for OpenSprinkler Pi running on a Rasberry Pi.
It has been working OK for a long time but recently I discovered that it died … could not contact it via webinterface or ssh.
Power reset got it airborne but after a couple of days … the same thing happened.
I decided to make an update so I ssh to it and login.
This is what I got.
I have Firmware version: 1.8.3
[email protected] ~/OSPi $ git pull
remote: Counting objects: 710, done.
remote: Compressing objects: 100% (333/333), done.
remote: Total 710 (delta 410), reused 644 (delta 366)
Receiving objects: 100% (710/710), 281.35 KiB | 47 KiB/s, done.
Resolving deltas: 100% (410/410), done.
+ 4496f83…aee472a master -> origin/master (forced update)
* [new branch] firmware_based -> origin/firmware_based
CONFLICT (add/add): Merge conflict in urls.py
CONFLICT (add/add): Merge conflict in templates/monthly.html
CONFLICT (modify/delete): static/scripts/java/svc1.8.3/home.js deleted in aee472a150e7c27cd7b1f0c68c47fe104a99696e and modified in HEAD. Version HEAD of static/scripts/java/svc1.8.3/home.js left in tree.
CONFLICT (modify/delete): sd_reference.txt deleted in aee472a150e7c27cd7b1f0c68c47fe104a99696e and modified in HEAD. Version HEAD of sd_reference.txt left in tree.
CONFLICT (add/add): Merge conflict in plugins/relay.py
CONFLICT (add/add): Merge conflict in plugins/monthly_adj.py
CONFLICT (add/add): Merge conflict in plugins/mobile_app.py
CONFLICT (add/add): Merge conflict in plugins/__init__.py
CONFLICT (content): Merge conflict in ospi.py
CONFLICT (add/add): Merge conflict in gpio_pins.py
CONFLICT (content): Merge conflict in README.md
CONFLICT (content): Merge conflict in .gitignore
Automatic merge failed; fix conflicts and then commit the result.
The next ‘git pull’ gives:
[email protected] ~/OSPi $ git pull
Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use ‘git add/rm
as appropriate to mark resolution, or use ‘git commit -a’.
How can this be fixed ?August 7, 2014 at 7:11 pm #27789
I am seeing the EXACT same problem on my board, too. I have the same firmware version and last year’s OSPi hardware (July 2013)
After I got into the mess above, I tried re-pulling the code cleanly (copied over this merged mess to a separate directory and re-creating the OSPi from a git clone) and then dropping in snames.json and options.txt from my old install, but that failed miserably. Completely down now.
Help!August 7, 2014 at 7:36 pm #27790
I’ve been seeing this problem about being unable to ssh in or contact the app via mobile or (old) web interfaces for quite some time (most of the summer). It will run about 1 week, maybe 2, and then this problem manifests. I have to reboot the OSPi to get back to normal.
I’ve tried updating the rpi OS (operating system, not Open Sprinkler) multiple times via apt-get update/upgrade but this hasn’t changed behavior.
I feel vindicated that another user is finally reporting this issue. Are you running longer term tests on older boards with older firmware?August 8, 2014 at 2:51 am #27791
I would suggest reviewing the instructions on the wiki:
It might be a good idea to use a new SD card also especially if you have had logging enabled.
The files from your old installation that contain your settings are:
sd.json – contains the option settings and other preeferences
snames.txt – contains station names
programs.json – contains irrigation program configurations.
DanAugust 8, 2014 at 8:46 am #27792
I removed OSPi directory and cloned a new OSPi directory from git hub … it works now and hopefully it will work in the future …
You said that ‘It might be a good idea to use a new SD card also especially if you have had logging enabled‘ but I can’t install OS & OSPi to a new card every time this problem occurs.
Should logging be disabled to avoid this ?
My OS is updated by ‘sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoclean && sudo apt-get autoremove && sudo apt-get clean’ so it must be a OSPi problemAugust 8, 2014 at 4:12 pm #27793
Just to be clear:
– I was indeed following those exact instructions. I had updated my setup to 2.0.x last fall with the proper git clone.
– I did nothing more than a git pull, and everything went to hell as zkab noted above. I had not modified any files directly myself.
– Like zkab, I keep my OSPi up to date with the latest updates and the latest Wheezy updates. This problem did not happen until this Spring, when I pulled a new version of OSPi
– I have logging DISABLED, I don’t even use that option
– Recommending that I do a full replace of the SD card every so often is insane. That doesn’t even make sense if I have logging OFF.
I have tried a clean git clone but it hasn’t addressed the sshd going down randomly after 1 week or so. It must also take out httpd as well, since I can’t use the web app or get mobile app to connect either.August 8, 2014 at 4:18 pm #27794
With the new version of the program, it is good to have logging enabled because the irrigation timeline on the home page shows log data in a graphical form.
The reason I suggested using a new CD card was because daver had mention that he has been running his system for a fairly long time. SD cards can wear out after writing a lot of files to them as explained on the wiki:
It is a good idea to use a different media to store the log data. I use an 8GB SanDisk Cruzer Fit USB flash drive on my OSPi. It is small enough to fit inside the case with the cover on.
DanAugust 9, 2014 at 8:46 pm #27795
I guess I should have realized the finite write cycle problem but never really thought about it.
What is the rough duty time of an SD card? Mine has only been in service for 12 months and like I said, no logging.
When should I expect it to crap out?
Any thoughts on the sshd problem that started happening in May?August 9, 2014 at 9:30 pm #27796
How are you connecting to the OSPi, wifi?
Since the ssh server is included with the OS and the OSPi web interface is part of the ospi software and you are loosing access to both, it sounds like it could be a problem in the communication link. Does the OSPi continue to run your sprinklers when you can’t access it?
DanAugust 13, 2014 at 4:24 pm #27797
I am using WiFi to access it, yes, that’s true.
The sprinklers do run even when I can’t connect (thank goodness, otherwise my lawn would be toast)
- You must be logged in to reply to this topic.