As Branko is turning in for the night, he has asked me to let everybody know that there is a new development snapshot for both ORx and Lighthouse.
As per usual there are various hazards associated with trying development snapshots.
According to Branko, this
The images can be found at the j.mp addresses:
j.mp/lighthouse-images
j.mp/orx-images
Unfortunately i don’t know much more than that, but i’m sure he’ll show up tomorrow to answer questions.
Enjoy!
Ben
What, no bugs to report? It must work flawlessly 
Chiming in to clarify: we’ve found a weird edge case where FSAL would stop receiving notifications about new downloads. It may or may not be related to the issue discussed by @kenbarbi, but we include a patch for that. There is also another small fix on Lighthouse where the FSAL log was not being returned in the diagnostics logs.
Finally, I’ve noticed there was a potential issue with postgres user permissions in the previous build. If you find that Librarian interface does not come up, and you’re on one of the previous snapshots (this doesn’t affect users coming from the 2.0.000 release), here is a simple fix:
sudo chown -R postgres.postgres /mnt/data/pgsqlsudo rebootLibrarian GUI should be available after the device is rebooted.
With snapshot 2.0.004, I started the Pi2 receiver with the WiFi adapter and HDStar tuner plugged. After the setup, the librarian started to download the files very quickly comparing with the previous versions and snapshots. Thanks @branko and team, also @kenbarbi 
Great news, Pradeeka, but I’m still having problems with Pages, Tweets, and my FSAL . Here’s a partial dump (whole log e mailed to Branko) of my System Log:
[2015-12-15 13:21:05 (+0000)] DEBUG Removing content ‘World Possible: RACHEL/Infonet Biovision’ from archive.
[2015-12-15 13:21:05 (+0000)] INFO Content removed from filesystem: ‘World Possible: RACHEL/Infonet Biovision’. Removing it from the library…
RuntimeError: FSAL could not connect to FSAL server
raise RuntimeError(‘FSAL could not connect to FSAL server’)
File “/usr/lib/python2.7/site-packages/fsal/client.py”, line 96, in _send_request
response = self._send_request(tostring(request_xml))
File “/usr/lib/python2.7/site-packages/fsal/client.py”, line 60, in wrapper
for e in self._get_changes_helper(limit):
File “/usr/lib/python2.7/site-packages/fsal/client.py”, line 227, in get_changes
for event in supervisor.exts.fsal.get_changes():
File “/usr/lib/python2.7/site-packages/librarian_content/tasks.py”, line 52, in check_new_content
changes_found = fn(supervisor)
File “/usr/lib/python2.7/site-packages/librarian_content/tasks.py”, line 23, in wrapper
fn(*args, **kwargs)
File “/usr/lib/python2.7/site-packages/librarian_core/contrib/tasks/scheduler.py”, line 35, in _execute
Traceback (most recent call last):
[2015-12-15 13:19:44 (+0000)] ERROR Task execution failed.
RuntimeError: FSAL could not connect to FSAL server
raise RuntimeError(‘FSAL could not connect to FSAL server’)
File “/usr/lib/python2.7/site-packages/fsal/client.py”, line 96, in _send_request
response = self._send_request(tostring(request_xml))
File “/usr/lib/python2.7/site-packages/fsal/client.py”, line 60, in wrapper
for e in self._get_changes_helper(limit):
File “/usr/lib/python2.7/site-packages/fsal/client.py”, line 227, in get_changes
for event in supervisor.exts.fsal.get_changes():
File “/usr/lib/python2.7/site-packages/librarian_content/tasks.py”, line 52, in check_new_content
changes_found = fn(supervisor)
File “/usr/lib/python2.7/site-packages/librarian_content/tasks.py”, line 23, in wrapper
fn(*args, **kwargs)
File “/usr/lib/python2.7/site-packages/librarian_core/contrib/tasks/scheduler.py”, line 35, in _execute
Traceback (most recent call last):
[2015-12-15 13:19:36 (+0000)] ERROR Task execution failed.
[2015-12-15 13:18:41 (+0000)] DEBUG Removing content ‘World Possible: RACHEL/Medline Medical Encyclopedia’ from archive.
[2015-12-15 13:18:41 (+0000)] INFO Content removed from filesystem: ‘World Possible: RACHEL/Medline Medical Encyclopedia’. Removing it from the library…
Let’s see what comes of this. Ken
@kenbarbi did you restart FSAL manually at some point?
for me
[1970-01-01 00:01:19 (+0000)] DEBUG Migration version for fsal.migrations.fs is 0.0
[1970-01-01 00:01:19 (+0000)] DEBUG Finished migrating to 01_00_add_filesystem_tables
[1970-01-01 00:01:19 (+0000)] DEBUG Finished migrating to 02_00_add_path_index
[1970-01-01 00:01:19 (+0000)] DEBUG Finished migrating to 03_00_add_events_table
[1970-01-01 00:01:19 (+0000)] INFO FSAL server started.
[1970-01-01 00:01:19 (+0000)] DEBUG Connected to ONDD at /var/run/ondd.ctrl
[1970-01-01 00:01:19 (+0000)] DEBUG DB refreshed in 28.587 ms
[1970-01-01 00:02:19 (+0000)] WARNING No data received from ONDD. Reconnecting
[1970-01-01 00:02:19 (+0000)] DEBUG Connected to ONDD at /var/run/ondd.ctrl
[2015-12-15 13:56:13 (+0000)] DEBUG Connected to ONDD at /var/run/ondd.ctrl
[2015-12-15 13:56:45 (+0000)] DEBUG Notification received for World Possible: RACHEL/Infonet Biovision/export/res/files/afmap.12262923718689282.200x200.png
[2015-12-15 13:56:45 (+0000)] DEBUG Notification received for World Possible: RACHEL/Infonet Biovision/export/res/files/3297.400x400.jpeg
[2015-12-15 13:56:45 (+0000)] DEBUG Updating db entry for “World Possible: RACHEL”
[2015-12-15 13:56:45 (+0000)] DEBUG Notification received for World Possible: RACHEL/Infonet Biovision/export/res/files/3335.280x185.clip.jpeg
[2015-12-15 13:56:45 (+0000)] DEBUG Updating db entry for “World Possible: RACHEL/Infonet Biovision”
[2015-12-15 13:56:45 (+0000)] DEBUG Notification received for World Possible: RACHEL/Infonet Biovision/export/res/files/1525.400x400.jpeg
[2015-12-15 13:56:45 (+0000)] DEBUG Updating db entry for “World Possible: RACHEL/Infonet Biovision/export”
@pradeeka I don’t see anything obviously wrong here or in the other logs.
@kenbarbi Can you tell me if you restarted FSAL manually? We couldn’t find anything wrong with the logs except a FSAL restart event, which would normally be a result of manual restart.
I did di a manual FSAL restart.
Is any one else using Lighthouse experiencing these kind of problems? Is there a possibility there is a problem with the internal chip or a component within my Lighthouse?
I’m going to run the ORxPi 2.0.004 on my older system and see what happens. Ken
According to the logs, there’s absolutely nothing out of the ordinary. That doesn’t rule out a possibility there is something that is not logged, of course, but still, it would be something quite unusual.
Ken, tomorrow I will test this latest snapshot image with my Lighthouse. time to sleep 
By the way, my ORxPi is up and running, but I had to connect by WiFi as I could not determine the unit’s IP address in my router. All my router says is orxpi on one of my ports - - no number as before with the Lighthouse which always appeared as 192.168.1.16.
Any suggestions? Ken
I’d recommend using Fing on a phone or Windows computer and scanning the network with it.
Thanks, but I really feel dumb about this - - all I had to do was look at the Network Connection tab in the dashboard, and it gave me the IP address. Strange as it might seem, it was 192.168.1.205! Thanks, I will try Fing and see if I get the same answer - - I should. Ken
I did get the same answer. Ken
Are you using Windows 10?
Hi Pradeeka - - I am using Windows XP on my computers and Jellybean Version 4.4.2. on my Android devices.
They all show the same thing. My receive configuration now is the ORxPi with version 2.0.004 running with the Geniatech receiver. I have a 16 GB SD chip installed. I can’t run both the ORxPi and Lighthouse since I only have 1 dish with LNB attached. My ethernet and WiFi hotspot are working fine on my ORxPi configuration.
I am receiving pages and Tweets from Galaxy 19 (which is not your satellite). The Tweets seem strange since I have been getting the same ones for many days on my Lighthouse running with various versions of the software. (Weird thou !?!?!)
I have taken snapshots of some of my screens 3 hours ago (15 Dec 2100 UTC), and will relook at them in 12 hours at (16 Dec 1230 UTC), and let you (and the world) know what I am seeing.
The thought crossed my mind that if we don’t see the same things, Galaxy 19 has some sort of problem the Outernet folks may need to investigate. But I suspect we should both see the same content in 12 hours. Ken in Annapolis, MD
Yes Ken, buy now I have to go to the office. Only I could check this after 8pm SL time. Now my ORxPi is switched off.
Any reason you’re not using the new release?
I thought v2.0.004 was the latest - - that’s what I have been working with.
It’s the version I use on my ORxPi and Lighthouse that only downloads a limited number of pages (18 pages in 15 hours) and 6 tabs of Tweets that never change but increment the date every day by one day. Here’s the end of the last page. Yesterday they were dated 12/14/2015 same time and content
These were the same Tweets yesterday, but were dated 12/14/2015 yesterday. For the last week with Galaxy 19 either with my Lighthouse or ORxPi using the various new versions, I always get the same top tweets shown here with that day’s current date
This has puzzled Branko, and Pradeeka is going to look at his system and tell me what he is getting off his satellite.
I’ll go and download the new 2.0.001 Hot Fix and try it on both. Ken
