1. Sid Price
  2. as Valentina DB Server
  3. Dienstag, Oktober 25 2016, 05:37 PM
  4.  Abonnieren via E-Mail
We have an embedded Linux (ARM) system with Valentina DB installed. We have noticed that there are many"autorestart" and "sleep 10" processes running on the system. Any ideas why this would happen?

At this time we don't know what the trigger for this is to happen, over the last week the system has been mostly running without any DB access at all.

Sid
Kommentar
There are no comments made yet.
Ruslan Zasukhin Akzeptierte Antwort
Hi Sid,

such behavior was couple of years ago for mac vserver, IF there was no any license file in folder "licenses",
but later we have allow to vserver start in this case with 1 connection.

In your case, this is not a mac, and this is not an old build.

I think Sergey will ask you for ZIP of logs.
Please open Mantis issue, and drop there one or few log files.

Another idea: may be vserver crashes on that computer?
Do you work with vserver in that time? Do you see any lost connections during work?
Kommentar
There are no comments made yet.
Sid Price Akzeptierte Antwort
Ruslan,
I have had to restart the device so I will monitor the problem and when it occurs again I will ZIP the logs.

VServer was not used during the time becuase I was working on another part of the system. I don't think VServer crashed, at least not while I was using the device.

Sid
Kommentar
There are no comments made yet.
Sid Price Akzeptierte Antwort
I have found the issue I was having and it was due to a networking script failing, this in turn meant the "autorestart" script of ValentinaDB was being run. Because the server was already running that new script failed but after pausing for a short time it would try again. Each time the server failed to start a new log file was created, this process was never ending.

We have fixed the script and the issue is not longer present.

Sid
Kommentar
There are no comments made yet.
  • Seite :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.