It would be great if you could provide vdsm and engine from the same time.

I see that engine logs end at 2016-10-12 10:51:36,336 and vdsm logs start at 2016-10-12 11:01:02,558

Thanks,
Piotr

On Wed, Oct 12, 2016 at 11:15 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:

On Wed, Oct 12, 2016 at 8:55 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:
Gianluca,

Please share engine log as well.

Thanks,
Piotr


Hello, I have not access right now to that server, but I have another quite similar environment (here the server is a Dell M910) with same behavior. It is at 4.0.4 too.
And also this environment was created in 3.6.x and then updated to various 4.0.x up to 4.0.4 now
vdsm version is now vdsm-4.18.13-1.el7.centos.x86_64
 
here vdsm.log in gzip format

and here engine.log in gzip format

[root@ractor ~]# systemctl status vdsmd
. vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/etc/systemd/system/vdsmd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2016-10-03 22:56:11 CEST; 1 weeks 1 days ago
  Process: 30970 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS)
  Process: 30974 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS)
 Main PID: 31166 (vdsm)
   CGroup: /system.slice/vdsmd.service
           ├─31166 /usr/bin/python /usr/share/vdsm/vdsm
           ├─31265 /usr/libexec/ioprocess --read-pipe-fd 61 --write-pipe-fd 59 --max-threads 10 --max-queued-req...
           ├─31280 /usr/libexec/ioprocess --read-pipe-fd 77 --write-pipe-fd 76 --max-threads 10 --max-queued-req...
           ├─31371 /usr/libexec/ioprocess --read-pipe-fd 105 --write-pipe-fd 103 --max-threads 10 --max-queued-r...
           ├─33870 /usr/libexec/ioprocess --read-pipe-fd 40 --write-pipe-fd 39 --max-threads 10 --max-queued-req...
           ├─33889 /usr/libexec/ioprocess --read-pipe-fd 48 --write-pipe-fd 47 --max-threads 10 --max-queued-req...
           ├─33896 /usr/libexec/ioprocess --read-pipe-fd 58 --write-pipe-fd 55 --max-threads 10 --max-queued-req...
           ├─33904 /usr/libexec/ioprocess --read-pipe-fd 73 --write-pipe-fd 72 --max-threads 10 --max-queued-req...
           └─33911 /usr/libexec/ioprocess --read-pipe-fd 98 --write-pipe-fd 96 --max-threads 10 --max-queued-req...

Oct 12 11:11:49 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:11:50 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:11:56 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:01 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:07 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:22 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:33 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:34 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:39 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Oct 12 11:12:45 mynewdomain vdsm[31166]: vdsm vds.dispatcher ERROR SSL error during reading d...eof
Hint: Some lines were ellipsized, use -l to show in full.
[root@ractor ~]#