Displaying 16 results from an estimated 16 matches for "20438".
Did you mean:
2038
2014 Jul 04
1
BUG: Authentication client sent unknown handshake command
...see the following
information in the logs:
Jul 4 04:04:36 mail dovecot: auth:
passwd-file(user,127.11.91.218,<nfkQjFT9vwCADFra>): no passwd file:
/etc/dovecot/imap.passwd
Jul 4 04:04:36 mail dovecot: auth: Error: BUG: Authentication client
sent unknown handshake command:
REQUEST?1183186945?20438?1?a8c7241e7b0778f9f0125da760cd16fa
Jul 4 04:04:36 mail dovecot: imap: Error: Authentication server didn't
send valid SPID as expected: MECH#011PLAIN#011plaintext
Jul 4 04:04:36 mail dovecot: imap: Error: Disconnected from auth
server, aborting (client-pid=20438 client-id=1)
Jul 4 04:04:36 ma...
2018 Jan 18
3
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...Ses we often catch the bug.
>> One of
>> VPSes sticks in 'in shutdown' state, no related 'qemu' process is
>> present,
>> and there is the next error in the log:
>>
>> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000:
>> 20438: warning : qemuGetProcessInfo:1460 : cannot parse process status
>> data
>> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000:
>> 20441: error : virFileReadAll:1420 : Failed to open file
>> '/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\...
2017 Jun 20
2
JIT, LTO and @llvm.global_ctors: Looking for advise
...to upload the patch
>since I need approval from Autodesk Legal department.
>
>Cheers,
>Benoit
>
>Benoit Belley
>Sr Principal Developer
>M&E-Product Development Group
>
>MAIN +1 514 393 1616 <tel:%2B1%20514%20393%201616>
>DIRECT +1 438 448 6304 <tel:%2B1%20438%20448%206304>
>FAX +1 514 393 0110 <tel:%2B1%20514%20393%200110>
>
>Twitter <http://twitter.com/autodesk>
>Facebook <https://www.facebook.com/Autodesk>
>
>Autodesk, Inc.
>10 Duke Street
>Montreal, Quebec, Canada H3C 2L7
>www.autodesk.com <http://ww...
2018 Jan 17
4
Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...l the VPSes.
When we try to 'shutdown' a number of VPSes we often catch the bug. One of
VPSes sticks in 'in shutdown' state, no related 'qemu' process is present,
and there is the next error in the log:
Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000:
20438: warning : qemuGetProcessInfo:1460 : cannot parse process status data
Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000:
20441: error : virFileReadAll:1420 : Failed to open file
'/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpuacct.usage':...
2018 Jan 17
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...to 'shutdown' a number of VPSes we often catch the bug. One of
> VPSes sticks in 'in shutdown' state, no related 'qemu' process is present,
> and there is the next error in the log:
>
> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000:
> 20438: warning : qemuGetProcessInfo:1460 : cannot parse process status data
> Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000:
> 20441: error : virFileReadAll:1420 : Failed to open file
> '/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpua...
2018 Jan 18
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...e try to 'shutdown' a number of VPSes we often catch the bug. One of
>VPSes sticks in 'in shutdown' state, no related 'qemu' process is present,
>and there is the next error in the log:
>
>Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.005+0000:
>20438: warning : qemuGetProcessInfo:1460 : cannot parse process status data
>Jan 17 13:54:20 server1 libvirtd[20437]: 2018-01-17 13:54:20.006+0000:
>20441: error : virFileReadAll:1420 : Failed to open file
>'/sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d36\x2dDOMAIN1.scope/cpuacct...
2017 Sep 28
1
one brick one volume process dies?
...-------------------------------------------------------------------------
Brick 10.5.6.49:/__.aLocalStorages/0/0-GLUS
TERs/0GLUSTER-CYTO-DATA???????????????????? 49161???? 0
Y?????? 1743719
Brick 10.5.6.100:/__.aLocalStorages/0/0-GLU
STERs/0GLUSTER-CYTO-DATA??????????????????? 49152???? 0
Y?????? 20438
Brick 10.5.6.32:/__.aLocalStorages/0/0-GLUS
TERs/0GLUSTER-CYTO-DATA???????????????????? 49152???? 0
Y?????? 5607
Self-heal Daemon on localhost?????????????? N/A?????? N/A
Y?????? 41106
Quota Daemon on localhost?????????????????? N/A?????? N/A
Y?????? 41117
Self-heal Daemon on 10.5.6.17??????????...
2017 Jun 20
2
JIT, LTO and @llvm.global_ctors: Looking for advise
Thanks for the hindsight.
I am currently working on a patch/potential fix which introduces a new
Linker::ImportIntrinsicGlobalVariables flag. The patch includes a unit
test reproducing the problem. Hopefully, that will help getting more
feedback.
Note that it might take a while before I am allowed to upload the patch
since I need approval from Autodesk Legal department.
Cheers,
Benoit
Benoit
2005 Sep 05
9
Samba Printing Extremely Slow from Windows XP
Hi,
I have setup samba server on my linux box (Fedora Core 4 with latest
samba, just updated via RHN) and has configured file sharing via samba
for this server and connecting to it from my windows xp box. So far,
everything works fine and it is very fast.
Then, I configured a printer, and shared it via samba. And, I can
see+connect to it from Windows XP and can even print. But, everything
2017 Sep 13
0
one brick one volume process dies?
These symptoms appear to be the same as I've recorded in this post:
http://lists.gluster.org/pipermail/gluster-users/2017-September/032435.html
On Wed, Sep 13, 2017 at 7:01 AM, Atin Mukherjee <atin.mukherjee83 at gmail.com>
wrote:
> Additionally the brick log file of the same brick would be required.
> Please look for if brick process went down or crashed. Doing a volume start
2017 Sep 13
2
one brick one volume process dies?
Additionally the brick log file of the same brick would be required. Please
look for if brick process went down or crashed. Doing a volume start force
should resolve the issue.
On Wed, 13 Sep 2017 at 16:28, Gaurav Yadav <gyadav at redhat.com> wrote:
> Please send me the logs as well i.e glusterd.logs and cmd_history.log.
>
>
> On Wed, Sep 13, 2017 at 1:45 PM, lejeczek
2005 May 12
2
Problem configuring speex 1.1.8
Can you send me the config.log?
Jean-Marc
Le vendredi 13 mai 2005 ? 00:16 +0200, Pierre a ?crit :
> Jean-Marc Valin wrote:
> > What platform (OS, compiler/version)
>
> GNU/Linux
> kernel 2.6.11.8
> gcc 3.4.3
>
> > Also, does it work with no options.
>
> No, I just tried with just "./configure" and I have the same error.
>
>
--
Jean-Marc
2005 May 13
0
Problem configuring speex 1.1.8
...igure:20224: result: yes
configure:20385: checking for short
configure:20409: gcc -c -s -O3 -march=i686 conftest.c >&5
configure:20415: $? = 0
configure:20418: test -z || test ! -s conftest.err
configure:20421: $? = 0
configure:20424: test -s conftest.o
configure:20427: $? = 0
configure:20438: result: yes
configure:20441: checking size of short
configure:20753: gcc -o conftest -s -O3 -march=i686 conftest.c -lwinmm -lm >&5
configure:20756: $? = 0
configure:20758: ./conftest
./configure: line 1: 31752 Segmentation fault ./conftest$ac_exeext
configure:20761: $? = 139
configu...
2005 May 13
1
Problem configuring speex 1.1.8
...20385: checking for short
> configure:20409: gcc -c -s -O3 -march=i686 conftest.c >&5
> configure:20415: $? = 0
> configure:20418: test -z || test ! -s conftest.err
> configure:20421: $? = 0
> configure:20424: test -s conftest.o
> configure:20427: $? = 0
> configure:20438: result: yes
> configure:20441: checking size of short
> configure:20753: gcc -o conftest -s -O3 -march=i686 conftest.c -lwinmm -lm >&5
> configure:20756: $? = 0
> configure:20758: ./conftest
> ./configure: line 1: 31752 Segmentation fault ./conftest$ac_exeext
> con...
2005 May 08
2
Problem configuring speex 1.1.8
...4: result: yes
configure:20385: checking for short
configure:20409: gcc -c -s -O3 -march=i686 -O3 -msse conftest.c >&5
configure:20415: $? = 0
configure:20418: test -z || test ! -s conftest.err
configure:20421: $? = 0
configure:20424: test -s conftest.o
configure:20427: $? = 0
configure:20438: result: yes
configure:20441: checking size of short
configure:20753: gcc -o conftest -s -O3 -march=i686 -O3 -msse conftest.c -lwinmm -lm >&5
configure:20756: $? = 0
configure:20758: ./conftest
./configure: line 1: 14953 Segmentation fault ./conftest$ac_exeext
configure:20761: $? = 1...
2015 Mar 25
3
[LLVMdev] Optimization puzzle...
Here's a version that doesn't try to do block deletion on it's own. If you
use -adce then -simplifycfg, you get what you want.
It passes all tests except one, which is that we delete an invoke of a pure
function, IE Transforms/ADCE/dce_pure_invoke.ll -
I'm not sure why that's bad.
The reason we delete it is because it returns false to
I.mayHaveSideEffects(), and in particular,