uploading through smoothwall router

[ftjandra]

Hi guys, yesterday I upgraded my router from smoothwall 1.0 to the beta5 2.0 version. Everything works great except that I can't upload anymore. I don't remember having to set up anything in the previous version. Here is what my error.log is filler up with:

ERROR: [000.000] {ncbi_http_connector.c, line 244} [HTTP] Error writing body at offset 12288
ERROR: [000.000] {ncbi_http_connector.c, line 244} [HTTP] Error writing body at offset 12288
ERROR: [000.000] {ncbi_http_connector.c, line 244} [HTTP] Error writing body at offset 12288
ERROR: [000.000] {ncbi_http_connector.c, line 101} [HTTP] Too many failed attempts, giving up
ERROR: [000.000] {foldtrajlite2.c, line 4616} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

Any ideas? I've got 8 machines waiting to upload... Thanks for the help!

--Ferdi

[bwkaz]

:idea:

Howard, is this the same problem as some are getting with NCBI + certain proxies?

In other words, is this a proxy that doesn't work, that someone (me? maybe...) could do some testing with?

Ferdi -- Do you know if Smoothwall installs a proxy? Do you know which one? I've never used Smoothwall myself, and I can't seem to find anything on their download page, other than that snort, squid, and ssh 3.7.1 are available. But I thought that squid worked with NCBI...

[ftjandra]

Hmm, I am not sure which proxy this version of smoothwall uses, but that certainly IS the problem! I disable the web proxy and now its uploading. But, I'd rather keep my proxy on, is there a way to get around this problem?

--Ferdi

[bwkaz]

Maybe. If we can figure out what it is, that'll help, because I might be able to grab its source and then run through the NCBI source.

Try ps ax >file1 with the proxy on, then ps ax >file2 with the proxy off. Then run diff -u file1 file2 to see what, if any, processes have been killed off when you shut down the proxy.

[ftjandra]

I couldn't get the -u option but here is the 'diff' output without it:

18c18
< 177 ? R 14:32 /usr/sbin/pppoe -p /var/run/pppoe.pid -I eth1 -T 80 -
---
> 177 ? R 14:31 /usr/sbin/pppoe -p /var/run/pppoe.pid -I eth1 -T 80 -
37,42c37
< 10004 ? S 0:00 /usr/local/squid/sbin/squid -D
< 10007 ? S 0:00 (squid) -D
< 10008 ? S 0:00 (unlinkd)
< 10019 ? S 0:00 sshd: root@ttyp2
< 10021 ttyp2 S 0:00 -bash
< 10032 ttyp2 R 0:00 ps ax
---
> 9987 ttyp1 R 0:00 ps ax

--Ferdi

[bwkaz]

Looks like it's using Squid.

Any way you can find out which version? You might be able to do /usr/local/squid/sbin/squid --version, but that's not guaranteed to work.

You might also search Smoothwall's package database. Dunno how that would work, though...

[ftjandra]

Ok, it was actually './squid -v' to get the version, here is the output:

Squid Cache: Version 2.5.STABLE1
configure options:

--Ferdi

[bwkaz]

2.5.stable1 then.

I'll grab NCBI again (grrr... lost my home directory a couple days ago...) and see if I can find anything. No guarantees, though, unfortunately...

(In other words, you'll have to keep the proxy off for the time being. :()

[Brian the Fist]

That error is NOT the usual one we see when a proxy is not working properly. And it should work with Squid. I believe that error means the upload got cut off, either at your end or our end. The only time I remember this error is when the 'upload receiver' on our server was corrupted and crashing, it produced this response on the client. This clearly is not the case here so I cannot tell you any more, but maybe it'll give you a clue what this proxy may be doing.

[bwkaz]

Awww, crud! :p I think I remembered you saying it worked with Squid, but I thought maybe there was a versioning issue or something.

Oh well, so much for that idea. Hmm...

I hate it when my assumptions are way wrong... :cry: :D