PDA

View Full Version : Slimserver causes load on Internet traffic...



gavlip@bigpond.net.au
2007-05-01, 03:49
I notice that when Slimserver is loaded (6.5.1) then this causes traffic on the internet/ADSL Modem.

If I stop slimserver then the traffic stops. Once restarted it starts up again. It seems to be about a packet a second. I don't have squeezenetwork on and I have my squeezebox off.

My internet provider has also registered the increased traffic.

Any ideas or help?

Thanks
Gavin

vain4
2007-05-01, 04:06
could it be one of the plugins? which ones are you using?

gavlip@bigpond.net.au
2007-05-01, 04:42
Whatever the default ones are by installation...
But would they still cause traffic if the squeezebox is off and not connected to squeezenetwork?
Don't know what traffic one packet a second is?

Skunk
2007-05-01, 05:20
One of the first things I do with new software is turn 'automatically check for updates' off. It sounds like slimserver may be listening for updates, which is just a guess, but you could try turning it off in Server Settings|Behavior.

jeffmeh
2007-05-01, 09:02
SlimServer broadcasts the date/time to the Squeezeboxes. Could it be trying to get out across your modem for some reason?

Mark Lanctot
2007-05-07, 12:53
SlimServer only needs internet access for:

1. Automatic updates (you can turn this off)
2. Internet radio (only if you are pulling streams from Internet radio)
3. Plugins (RSS feeds, weather, etc.)
4. Public SlimServer access if you've chosen to do so.

Item 2, it may query the station for track data even when the Squeezebox is off. Note, the Squeezebox is never really off, it's idle.

Item 3, these plugins can be active as sceensavers in any mode, including idle, and even if brightness is set to 0.

Item 4, you generally have to go out of your way to do this unless you have no firewall or router. Do you have a firewall or router?

If you do have a firewall, you can disallow SlimServer Internet access if you're willing to lose items 1-4. Do not block local network traffic though or your players will stop working.

mlsstl
2007-05-07, 14:32
That is a good question about your hardware configuration. Are you behind a router or is your PC directly connected to your ADSL modem? If the latter case, what IP is your Squeezebox using and/or what DHCP server is assigning an IP address to it?

You said virtually nothing about your home network configuration so I'm wondering if the problem ties to that.

JJZolx
2007-05-07, 15:32
could it be one of the plugins? which ones are you using?

And aren't all of the included plugins enabled by default?

Besides turning off automatic checks for updates, the first thing I do is disable all unused plugins. The only ones I find necessary are the 'Date and Time Screensaver' and 'Random Mix'. It will depend, though, on whether you need things like iTunes or MusicMagic integration.

cognoquest
2007-05-30, 21:32
I have the exact same problem; I also have erratic startups of my Squeezeboxes(Yep they turn on by themselves).
This all started when I upgraded my version of Clarkconnect from version 3.2 to 4.1. I have an image of my server configuration prior to the upgrade, I went back to it to confirm that I had no problem then, all seem to be working find on the previous version of clarkconnect.
I suspect the traffic increase is coming from the slimserver service, could also be coming from my Squeezeboxes.
The traffic increase is in one direction, outgoing from my server, the incoming traffic does not seem to be affected. The output is approximately 70.0 to 80.0 k per second.
The slimserver is running on a separate server from my gateway.

Since this is an outgoing traffic problem, I turned on the http, http_async, http_verbose debugging.

Here is a sample of what I get:

2007-05-30 22:56:29.2103 sendstreaming response begun...
2007-05-30 22:56:29.2117 Closing streaming socket.
2007-05-30 22:56:29.2131 Closing streaming file.
2007-05-30 22:56:29.2162 Streaming client closed connection...
2007-05-30 22:56:29.6278 Accepted connection 1 from 66.249.65.11
2007-05-30 22:56:29.6331 reading request...
2007-05-30 22:56:29.6352 HTTP request: from 66.249.65.11 (HTTP::Daemon::ClientConn=GLOB(0xc669ad0)) for GET HTTP/1.1 /status_header.html?p0=mixer&p1=volume&p2=70&player=00%3A04%3A20%3A06%3A39%3Ad4
2007-05-30 22:56:29.6390 HTTP parameter p0 = mixer
2007-05-30 22:56:29.6413 HTTP parameter p1 = volume
2007-05-30 22:56:29.6431 HTTP parameter p2 = 70
2007-05-30 22:56:29.6457 HTTP parameter player = 00:04:20:06:39:d4
2007-05-30 22:56:29.6523 processURL Clients: 66.249.65.11:35228 192.168.1.91:34549
2007-05-30 22:56:29.6599 Generating response for (htm, text/html) status_header.html
2007-05-30 22:56:29.6632 generating from include.html
2007-05-30 22:56:29.6840 generating from select_option.html
2007-05-30 22:56:29.6999 generating from select_option.html
2007-05-30 22:56:29.8019 generating from status_header.html
2007-05-30 22:56:29.9136 End request: keepAlive: [1] - waiting for next request for HTTP::Daemon::ClientConn=GLOB(0xc669ad0) on connection = Keep-alive

2007-05-30 22:56:29.9490 Sent 322 to 66.249.65.11
2007-05-30 22:56:29.9510 More to send to 66.249.65.11
2007-05-30 22:56:30.0605 Sent 8191 to 66.249.65.11
2007-05-30 22:56:30.0621 No more messages to send to 66.249.65.11
2007-05-30 22:56:30.0958 No segment to send to 66.249.65.11, waiting for next request..
2007-05-30 22:56:39.2637 reading request...
2007-05-30 22:56:39.2650 Client at 66.249.65.11 disconnected. (half-closed)

2007-05-30 22:57:43.4112 Accepted connection 1 from 66.249.65.11
2007-05-30 22:57:43.4165 reading request...
2007-05-30 22:57:43.4188 HTTP request: from 66.249.65.11 (HTTP::Daemon::ClientConn=GLOB(0xc7da95c)) for GET HTTP/1.1 /music/1599/download/
2007-05-30 22:57:43.4316 processURL Clients: 66.249.65.11:35228 192.168.1.91:34549
2007-05-30 22:57:43.4343 Generating response for (htm, text/html) music/1599/download/
2007-05-30 22:57:43.4377 generating from include.html
2007-05-30 22:57:43.4703 Opening Slim::Schema::Track=HASH(0xc7d3ed8) to stream...
2007-05-30 22:57:43.4789 End request: keepAlive: [1] - waiting for next request for HTTP::Daemon::ClientConn=GLOB(0xc7da95c) on connection = Keep-alive

2007-05-30 22:57:43.4824 sendstreaming response begun...
2007-05-30 22:57:43.4850 Streamed 345 to 66.249.65.11
2007-05-30 22:57:43.4883 sendstreaming response begun...
2007-05-30 22:57:43.4908 (audio: 32768 bytes)
2007-05-30 22:57:43.4945 Streamed 32768 to 66.249.65.11
2007-05-30 22:57:43.4970 sendstreaming response begun...
2007-05-30 22:57:43.4998 (audio: 32768 bytes)
2007-05-30 22:57:43.5038 Streamed 32768 to 66.249.65.11
2007-05-30 22:57:43.5356 sendstreaming response begun...
2007-05-30 22:57:43.5380 (audio: 32768 bytes)
2007-05-30 22:57:43.5402 Streamed 32768 to 66.249.65.11
2007-05-30 22:57:43.9548 sendstreaming response begun...
2007-05-30 22:57:43.9566 (audio: 32768 bytes)
2007-05-30 22:57:43.9592 Streamed 32768 to 66.249.65.11
2007-05-30 22:57:44.3636 sendstreaming response begun...
2007-05-30 22:57:44.3654 (audio: 32768 bytes)
2007-05-30 22:57:44.3675 Streamed 32768 to 66.249.65.11
2007-05-30 22:57:44.7704 sendstreaming response begun...
2007-05-30 22:57:44.7724 (audio: 32768 bytes)
2007-05-30 22:57:44.7750 Streamed 32768 to 66.249.65.11
2007-05-30 22:57:45.1435 sendstreaming response begun...
...
And it goes on and on.

I have had to turn off the slimservice service until a solution is found (No complaints from my provider yet but do not want to go there).
I am open to any suggestions ??

Philippe

bpa
2007-05-30, 23:55
Checking who owns 66.249.65.11 - returned the following:

IP: 66.249.65.11
Reverse: crawl-66-249-65-11.googlebot.com
Aliases:
Prefix: 66.249.65.0/24
Prefix Name: Google REACH (Customer Route)
AS: 15169
AS Name: Google Google, Inc


If this is true, looks like Google wants to know more about youer music !

oreillymj
2007-05-31, 04:38
I wonder if that explains why music started playing on my SB3 at 3:00am last week and frightened the crap out of my wife, who thought there was someone in the house.

I closed the virtual server ports defined in the Router. And put an active block on incoming server connections going to Slim.exe.

I seem to remember Andy making some sort of change recently which uses google.com to determine DNS server.
Wonder if that request added the i.p. to Google's list of i.p. to spider.

bpa
2007-05-31, 05:18
I think the google.com lookup is just to your local DNS server - I don't think it results in a message to google itself.

cognoquest
2007-05-31, 07:04
I have blocked on my gateway all outgoing traffic to 66.249.65.0/19. (The incoming/outgoing are from the perspective of my server)

I believe things have quiet down (should I be touching wood right now?). Not easy to monitor this one. At least all incoming/outgoing statistics seem to look ok for now; can not tell if the erratic behavior is gone only time will tell about that one.

Have I lost much from my internal network not being able to do lookupís on 66.249.65.0/19?

OrgName: Google Inc.
OrgID: GOGL
Address: 1600 Amphitheatre Parkway
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US

NetRange: 66.249.64.0 - 66.249.95.255
CIDR: 66.249.64.0/19
NetName: GOOGLE
NetHandle: NET-66-249-64-0-1
Parent: NET-66-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.GOOGLE.COM
NameServer: NS2.GOOGLE.COM
NameServer: NS3.GOOGLE.COM
NameServer: NS4.GOOGLE.COM

If yes I can always firewall my internal server where the slimserver service resides (do not really want to) and reopen my gateway outgoing firewall.

Also have I done any other injury to the slimserver service by doing so?

I know this is not a solution more of a patch. If anything I can do or should do to help resolve this let me know.

Philippe

cognoquest
2007-05-31, 07:21
Note:

It seem I have confused 'CIDR: 66.249.64.0/19' with 66.249.65.0/19? and blocked 66.249.65.0/19.
Maybe I should have blocked a bigger range anyways it is still working.

Philippe

andyg
2007-05-31, 07:27
When SlimServer first starts up, we do a DNS lookup for www.google.com, but this only hits your local DNS server(s), and only once at startup. We don't actually connect to Google for anything, unless you've got an RSS feed there or something.

cognoquest
2007-05-31, 09:35
I believe you Andy. But my Slimserver logs where showing non stop requests to 66.249.65.11 until I blocked these Ipís.
Interesting that you are taking about feeds and I do not know if this is related but the erratic behavior (happy to hear that oreillymj had the same problem, thought for a while I was loosing it) of my Squeezeboxes would be that they would turn on by themselves on different feeds which I had never listened to.

I am grasping at straws here. I still believe this has to do with my Clarkconnect upgrade CentOS 4.4 and Perl version: 5.8.5, I did not have this problem prior to the upgrade and seen previous problems here with this new Perl/OS combination.

Maybe others by seeing this post will start looking at their outgoing statistics more closely. I found this problem by accident; I have been trying to understand the erratic behavior of my Squeezeboxes (I thought it might be my sons playing tricks on their dad) for the past two weeks until I came upon this other traffic problem.

Philippe

bpa
2007-05-31, 09:41
If you look at the log - you can see it is Google crawler going over your Slimserver web interface - downloading music from your webclient. It is not slimserver requesting anything from google.


2007-05-30 22:57:43.4188 HTTP request: from 66.249.65.11 (HTTP::Daemon::ClientConn=GLOB(0xc7da95c)) for GET HTTP/1.1 /music/1599/download/

andyg
2007-05-31, 09:52
Ah yes, there you go. GoogleBot is crawling your SlimServer. You need to firewall it!

cognoquest
2007-05-31, 10:54
Bravo guys. I feel like an idiot. My first reaction, no way. Second check at my gateway firewall configuration et voila an Open Port Forward for port 9000.

Thanks many times,
Philippe

JimC
2007-05-31, 22:55
GoogleBot is crawling your SlimServer. You need to firewall it!

Now that was funny.

seanadams
2007-05-31, 23:20
Ah yes, there you go. GoogleBot is crawling your SlimServer. You need to firewall it!

Should we add a robots.txt?

SuperQ
2007-05-31, 23:22
When SlimServer first starts up, we do a DNS lookup for www.google.com, but this only hits your local DNS server(s), and only once at startup. We don't actually connect to Google for anything, unless you've got an RSS feed there or something.

lol! I guess you trust google's DNS more than you trust www.slimdevices.com.

Speaking of Google...

There are a couple things that should be fixed.. The slimserver should probably include a robots.txt to make GoogleBot not index them if someone connects it to the internet. Either that or slimserver could detect the User Agent string and do something different if it sees GoogleBot, MSNBot, etc..

GoogleBot could also detect slimservers and avoid them.. I can look into that..

SuperQ
2007-05-31, 23:34
When SlimServer first starts up, we do a DNS lookup for www.google.com, but this only hits your local DNS server(s), and only once at startup. We don't actually connect to Google for anything, unless you've got an RSS feed there or something.

really.. as much as google is awesome.. you should probably do something like randomly pick [a-m].root-servers.net and do that lookup.

fuzzyT
2007-06-01, 09:38
seanadams wrote:

> Should we add a robots.txt?

Seemingly an excellent idea.

I can't imagine why you /would/ want your SS indexed by Google, so IOW
no downside.

andyg
2007-06-01, 10:04
I've added a robots.txt file, good idea.

Changing the domain we look up may also be a good idea, I didn't think of using root-servers.net.

oreillymj
2007-06-07, 13:32
Strange, I came home from work today, and my SB3 was playing again.
This is the third time this has happened in recent months. Even though my taste in music is excellent;-) ,I'm sure the neighbours don't appreciate it, especially at 3am.
My SB2 in the kitchen has never done this.

I've firewalled off my network so the Slimserver web-site is inaccessable to the outside world.

Both the model/wireless router & firewall on my PC all block off port 9000

Anyone got any ideas why this might be happening?

JJZolx
2007-06-07, 13:38
Strange, I came home from work today, and my SB3 was playing again.
This is the third time this has happened in recent months. Even though my taste in music is excellent;-) ,I'm sure the neighbours don't appreciate it, especially at 3am.
My SB2 in the kitchen has never done this.

I've firewalled off my network so the Slimserver web-site is inaccessable to the outside world.

Both the model/wireless router & firewall on my PC all block off port 9000

Anyone got any ideas why this might be happening?

At work, do you listen to music from your SlimServer? I find that it's common for the players to get mixed up in the browser and when I think I'm playing something to Softsqueeze on my work PC, it actually plays to one of my players at home.

snarlydwarf
2007-06-07, 13:42
At work, do you listen to music from your SlimServer? I find that it's common for the players to get mixed up in the browser and when I think I'm playing something to Softsqueeze on my work PC, it actually plays to one of my players at home.

My gf often starts music in the bedroom (get your mind outta the gutter! geesh) for some reason. My browser never does that, and her bookmark looks right to me, but just launching firefox and choosing the bookmark starts things playing.

May be something to do with firefox's "should I restore that last session?" thingie. I always figure that "you barfed on it last time, NO" is the correct answer, but she may choose something different.

JJZolx
2007-06-07, 13:56
May be something to do with firefox's "should I restore that last session?" thingie.

Probably just subtle bugs in the javascripting and use of cookies to keep track of the current player. Complicated infinitely by the use of frames for the interface.

oreillymj
2007-06-07, 16:08
I set up internet access to test out streaming to work, but my DSL uplink wasn't fact enough.

So it's been disabled.

Also I rarely/never leave the Slim web ui open in a browser on the server and it wasn't open today.