Internal Server Error 500, Undefined offset: 2 when updating

by lcd, Thursday, March 28, 2013, 13:18 (4367 days ago) @ lcd

Checking again, it's definitely stopping early. If anyone has any clues as to why and how to fix it, please let me know.

Sorry for the late reply, was away from the computer for a few days.

It looks like its some kind of general apache problem rather then a selfoss problem - enabling debug in config.ini on selfoss has this at the end of the update

• 03-28-13 9:34:17 Debug Memory usage: 7830112
  
• 03-28-13 9:34:17 Debug Memory peak usage: 21744664
  
• 03-28-13 9:34:17 Debug start insertion of new item "Giving a CNC knitting machine a new brain"
  
• 03-28-13 9:34:17 Debug item content sanitized
  
• 03-28-13 9:34:17 Debug use last icon: http://s1.wp.com/wp-content/themes/vip/hackaday2/images/favicon.ico?m=1353160633g
  
• 03-28-13 9:34:17 Debug item inserted
  
• 03-28-13 9:34:17 Debug Memory usage: 7848952
  
• 03-28-13 9:34:17 Debug Memory peak usage: 21744664
  
• 03-28-13 9:34:17 Debug destroy spout object
  
• 03-28-13 9:34:17 Debug ---
  
• 03-28-13 9:34:17 Debug start fetching source "Hanging Rock Comics (id: 209)
  
• 03-28-13 9:34:17 Debug spout successfully loaded: spouts\rss\feed
  
• 03-28-13 9:34:17 Debug fetch content
  
• 03-28-13 9:34:18 Debug minimum date: 2013-02-26 09:34:18
  
• 03-28-13 9:34:18 Debug start item fetching
  
• 03-28-13 9:34:18 Debug start insertion of new item "blahblah1"
  
• 03-28-13 9:34:18 Debug item content sanitized

which all looks normal.

Apaches log file has this:

[Thu Mar 28 09:34:20 2013] [error] [client 127.0.0.1] Undefined offset: 2

The previous line is from 6 minutes before that, and just about me using update with lower case rather then update with upper case:

[Thu Mar 28 09:28:35 2013] [error] [client 127.0.0.1] Negotiation: discovered file(s) matching request: /var/www/selfoss/update (None could be negotiated).

But that still doesn't give me any more clue as to what the error is.

Does no one else have this update issue?

This time, the update ran for 4 or 5 minutes and pulled around 270 posts - but looking at the comparative time in Google Reader, boing boing (which is only one of the subscriptions) appears to have had roughly this many alone over that time period.

Could it be working and have some other criteria google reader doesn't have for collecting posts? Or is the update process crapping out early? Any clues or anywhere else I should look?