SOLVED: Server unavailable to at least some users

SOLVED: Server unavailable to at least some users

Postby DFLiddle » 23 Nov 2012, 18:52

We have TDPS 1.0.047 installed in Ubuntu 12.04.1 LTS, running as an OpenVZ container on Proxmox VE 1.9. The data is on an NFS share stored on a Synology RS407 NAS. Access from the WAN is managed by NAT on a ZyWALL USG-200.

This week, I noticed that a change I made at work from my laptop did not find its way to my iPad at home. When I returned to the office, I noticed that the space I use indicated "Status: Offline" (barred red circle over the folder). My colleague confirms that he is having the same problem with our space, but another user indicated today that his spaces seem fine. We have several users of other spaces stored on our TDPS, but they are in many different places and difficult to contact, so I can't be certain that it's not working for everyone. The last access date I see on an individual file in the repository is "Nov 22 11:06".

Last week (on 2012-11-15), I successfully followed the instructions in this forum for running tdpsd as a service by a non-root user. The server and software continued to work as they should. Since then, there have been no other changes to the server. I checked the history for unattended-updates to make sure that a package hadn't been installed that might have broken the service, but there was nothing during the time period. The tdpsd logs and the watch-tdps tool do not show anything that seems much out of the ordinary, though I cannot be sure of the following, which I have seen reported elsewhere:

Code: Select all
121122 14:03:54 [Warning] Got SIGPIPE, ignored
121122 14:03:54 [Error] NetworkHandler1: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): '86.168.***.***'


Numerous similar errors also appear before the changeover to running as a service. There are some other lines that I do not understand:

Code: Select all
121115 01:12:48 [Error] NetworkHandler12: MD5 Check failed on /mnt/TeamDrive/12/data/PVSQZ9800AH8Q004PPTCJZZ552GXGC2Z
121115 01:12:48 [Error] NetworkHandler12: Length read: 12544000, will reset to: 12544000
121115 01:12:50 [Error] NetworkHandler2: MD5 Check failed on /mnt/TeamDrive/12/data/PVSQZ9800AH8Q004PPTCJZZ552GXGC2Z
121115 01:12:50 [Error] NetworkHandler2: Length read: 0, will reset to: 0
121115 01:13:14 [Error] NetworkHandler14: MD5 Check failed on /mnt/TeamDrive/12/data/PVSQZ9800AH8Q004PPTCJZZ552GXGC2Z
121115 01:13:14 [Error] NetworkHandler14: Length read: 0, will reset to: 0
121115 01:13:15 [Error] NetworkHandler4: MD5 Check failed on /mnt/TeamDrive/12/data/PVSQZ9800AH8Q004PPTCJZZ552GXGC2Z
121115 01:13:15 [Error] NetworkHandler4: Length read: 0, will reset to: 0


Are these clues to the problem? What do they mean? What other information could I provide that would help those of you with more experience to guide me? One step I plan to take this weekend is to restart the gateway device and perhaps update its firmware, which has seen its share of problems in the past few months. There are entries in its logs, with respect to traffic to the TDPS, that seem to indicate a problem.

One odd thing that just happened was that I turned space synchronization on for two spaces that I created for other people to use — but which I didn't need on my own computer. Then I chose "Restore Missing Files", which worked! However, just a few minutes later, those spaces now appear offline. This seems bizarre to me.

Many thanks for your considerate and gracious help!
Last edited by DFLiddle on 29 Nov 2012, 14:26, edited 2 times in total.
DFLiddle
 
Posts: 7
Joined: 04 Aug 2012, 17:58

Re: Server unavailable to at least some users

Postby EPruehs » 26 Nov 2012, 14:52

Please try to increase the maximum-connections to 100 or more.
EPruehs
TeamDrive Team Member
 
Posts: 169
Joined: 17 Jul 2008, 18:05

Re: Server unavailable to at least some users

Postby DFLiddle » 27 Nov 2012, 12:55

EPruehs wrote:Please try to increase the maximum-connections to 100 or more.


After receiving the above advice, I changed the number of allowed connections to 120. The only entries in the server log since that time are:

Code: Select all
121126 14:40:04 TeamDrive Personal Server, version 1.0.047 (CSLib 1.0.0(Built Aug 15 2011 05:30:02)), running as "tdpsd"
Command line: /opt/tdpsd/tdpsd
121126 14:40:04 [Note] TeamDrive Personal Server listening on port 37655
121126 14:40:05 [Warning] Got SIGPIPE, ignored
121126 14:40:05 [Error] NetworkHandler6: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): '88.151.***.***'
121126 14:40:06 [Warning] Got SIGPIPE, ignored
121126 14:40:06 [Error] NetworkHandler8: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): '86.168.***.***'


I can confirm that the number of entries listed by the command pstree -p is correct. Traffic is being directed to the server as it should be from both external and internal sources. My gateway device indicates one session with the server, but I cannot personally identify the possibly successful (lucky?) user. Looking at the packets being sent from my computer to the server, I do see a number of them being identified (in Wireshark) with the "Bad TCP" flag. Unfortunately, I am not knowledgeable enough to interpret what I see in those logs. I am in the process of matching such entries with the debug entries of our gateway/firewall device specifying "invalid state detected", but I am unsure of those as well. They're rather vague.

If they would be helpful, I can include logs from the server, the gateway, my PC and my iPad.
DFLiddle
 
Posts: 7
Joined: 04 Aug 2012, 17:58

SOLVED: Server unavailable to at least some users

Postby DFLiddle » 29 Nov 2012, 14:25

It would help to have answers to the side questions I posed in my request for help, but I will report that re-applying the permissions needed for the tdpsd user on the NFS share appears to have resolved the problem. If the issue should reoccur, I certainly know now where to look first.
DFLiddle
 
Posts: 7
Joined: 04 Aug 2012, 17:58

Re: SOLVED: Server unavailable to at least some users

Postby TDRQ » 04 Nov 2016, 18:10

Hello DFLiddle,

kindly advise how you had resolved the previously described issue as we are currently facing the same error Messages on our Server.

Code: Select all
16:59:27 [Note] TeamDrive Personal Server listening on port 37655
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler2: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler6: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler3: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler4: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Error] NetworkHandler1: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'


Maximum Connections are set to 120 and chmod -R 755 /tdpsd is set.
TDRQ
 
Posts: 2
Joined: 04 Nov 2016, 18:06

Re: SOLVED: Server unavailable to at least some users

Postby DFLiddle » 07 Nov 2016, 09:59

@TDRQ, I used the chown command to make the tdpsd user and group the owners of the data directory and its child objects. It's probable that I stopped the server before executing the command.


TDRQ wrote:Hello DFLiddle,

kindly advise how you had resolved the previously described issue as we are currently facing the same error Messages on our Server.

Code: Select all
16:59:27 [Note] TeamDrive Personal Server listening on port 37655
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler2: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler6: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler3: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Warning] Got SIGPIPE, ignored
161104 17:02:40 [Error] NetworkHandler4: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'
161104 17:02:40 [Error] NetworkHandler1: void CSSocket::writeBlock(CSSocket.cc:202) Broken pipe (32): 'XX.XXX.X.XXX'


Maximum Connections are set to 120 and chmod -R 755 /tdpsd is set.
DFLiddle
 
Posts: 7
Joined: 04 Aug 2012, 17:58

Re: SOLVED: Server unavailable to at least some users

Postby TDRQ » 08 Nov 2016, 11:30

Thank you for you prompt assistance DFLiddle!
I have implemented your advise and will monitor the log file carefully during the next days. I will Report latest by the end of the week if the chown command solved the issue respectively this error message/different messages are recorded.
TDRQ
 
Posts: 2
Joined: 04 Nov 2016, 18:06


Return to TeamDrive Personal Server

Who is online

Users browsing this forum: No registered users and 3 guests

cron