dr-tart;226797 Wrote: 
> After last weekend's lastfm downtime, my slimserver.log file started
> expanding at an enormous rate - about 100MB an hour. It was full of
> millions of lines like 
> 
> Select task failed: Not a SCALAR reference at
> /usr/local/slimserver/Slim/Networking/
> Select.pm line 278.
> 
> I've found other posts from people with the same error and so I've
> worked around it by removing my /tmp/PendingSongFile_user.txt file.
> lastfm is scrobbling away again, and my log file is under control.
> 
> I've tried to investigate, and switched on plugin and async http
> debugging. The resulting log file can be found at
> 
> http://www.torturkammer.eclipse.co.uk/slimserver.log.gz
> 
> I guess the interesting lines are:
> 
> 2007-09-12 20:08:24.0359 Scrobbler: FAILED Plugin bug: Not all request
> variables are set - no POST parameters
> .
> INTERVAL 1
> 
> 2007-09-12 20:08:24.0359 Scrobbler: AudioScrobbler POST Error:  Plugin
> bug: Not all request variables are set
> - no POST parameters.
> 
> My pending song file is at
> 
> http://www.torturkammer.eclipse.co.uk/PendingSongFile_username.txt.gz
> 
> copying this file to my /tmp directory immediately causes the problem
> to recur.
> 
> Hope this helps in tracking down the cause

The most common reason for the 'Not all request variables are set - no
POST parameters' bug isn't a broken client but a broken server. For no
seemingly apparent reason, the server will give up waiting for incoming
data and just claim that you've not sent any post paramters, despite the
fact that they arrive at the server a moment later.

For more details, consult
http://www.last.fm/forum/21716/_/201367/1#f2576340 and replies.


-- 
gerph
------------------------------------------------------------------------
gerph's Profile: http://forums.slimdevices.com/member.php?userid=1819
View this thread: http://forums.slimdevices.com/showthread.php?t=38347

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins

Reply via email to