Whoops. My misunderstanding. I’ll look forward to the next beta release.
And it’s now available.
Nice! Got it. Installed and running. Fingers crossed!
3 Likes
The good news is that the DT3 web server lasted longer and through more use than it has in months. The bad news is that it still stopped responding, though this time something like a week-and-a-half after being started. I know it was working fine yesterday because I used it a lot. This morning it wasn’t working. And I actually see the following error in the log window:
9/6/22, 1:30:05 AM | Request failed with http status code 503 | CKErrorDomain 6
I’m uploading the logs as before. Let me know if I can provide anything else.
Archive.zip (93.1 KB)
1 Like
I don’t use or even own DT Server; but I love the way you are working together with DEVONtech to pinpoint the problem and the solution. That beats moaning about the problem hands down and you are helping others along the way. So thank you for your tone, your perseverance, your insight. I really appreciate it!
5 Likes
Thank you for the logs! The new timeout actually worked more than 100 times as expected and that’s probably the reason why the server worked longer than ever but finally a bad request caused the issue but it’s unclear why. Maybe a bot scanning servers & ports?
Wow, that timeout mechanism is clearly a winner. As to the “bad request”, is there some way to armor the server against that so that a “bad request” doesn’t kill it? I don’t have any bots scanning my network of which I’m aware (I have a Firewalla Gold network appliance monitoring for that kind of thing too, so I think I’m pretty safe on that point).
I meant to mention too that the new betas seem to give Firefox fits. I can reproduce the bug on multiple machines on different OSes. The markdown editing pane gets limited to roughly 3 lines of text maximum on Firefox now with these betas. The prior release didn’t have the issue. I’ll attach a screen shot of one of my notes. Notice in particular what a tiny fraction of the editing pane the scrollbar takes up. It makes editing notes basically impossible in Firefox.
Let me know if I should file a separate bug or post something separately somewhere.
According to the log it wasn’t an issue for the server actually which just handled the request as expected and finally closed the connection again but I’m not sure whether it might have been an issue for Bonjour. Did you check whether the server was still responsive on the server’s machine or another machine/browser?
Unfortunately there’s a zillion of bots on the internet scanning IP addresses for open ports, known security issues etc.
I did check from other browsers on the same machine and on another machine, none of which worked. I confess I forgot to check a browser on the local machine; I’ll have to put up a sticky note or something so I quit forgetting. For what it’s worth, however, I don’t believe I’ve enabled bonjour sync on that machine. I can confirm that if it matters.
The server is based on Bonjour which handles TCP/IP and ports, it’s not related to the sync which just offers a Bonjour option too.
I fear I’m going to need to read that many more times with a much fresher brain until it makes sense. I’ll get back to you.
Another day, another failure. Though this time the server lasted over a week again. I’m going to send the logs to y’all privately this time as you suggested.
I thought I would post again to my original forum topic for sake of closure for any watchers or future visitors. I’ve continued to work with the DEVONthink folks since the last update here via private messages instead. After a series of bug-fixes over several releases, the logs taken after failure have shown no more issues on the DEVONthink side of things.
I still continue to have the issue, but I’m beginning to think there is something going on with either this installation of macOS or the computer itself as I’ve now started to see similar behavior from both SSH and remote screen sharing. I now have a single cron job in my personal account to restart DT3 (using the script shown above in this thread), and I have two more cron jobs queued up under the super-user account that restart the SSH and remote screen sharing service respectively.
With those three cron jobs in place, I’m happy to say that the machine in question hasn’t failed to respond now for a month. That’s good enough for me, so I’m calling it resolved. It’s still a little mysterious why this machine simply drops network connections to the outside world like no other computer I’ve ever owned, but it is just over six years old, so maybe it’s just getting old and grumpy like me. Best wishes to anyone else having these kinds of issues.
5 Likes
Thanks for the update, highly appreciated.
2 Likes