search for: ratchet

On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: internal error: Failed to reserve port" error is received and migration does not succeed: virsh # migrate cartridge qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --verbose error: internal error: Failed to reserve port 49153 virsh # On target host with debug logs, nothing interesting but the error itself is found in the logs ... 2020-10-12 02:11:33.852+0000: 6871: debug : qemuMonitorJSONIO...

Hey all, With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in tunneled mode does not work for me: virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --tunneled --p2p error: internal error: qemu unexpectedly closed the monitor: Receiving block device images Error unknown block device 2020-08-15T21:21:48.995016Z qemu-system-x86_64: error while loading state section id 1(block) 202...

Hi Maxence, > Fyi, i've updated to 4.7.1, the dbcheck still not fix the broken links, > is the fix you talk about planned for a future release ? > > Our customer reported me, some users have issues when their logon server > is DC1 but not when it's DC2. > > On DC1 some users have access to all shares, some doesn't have any > access at all. actually this last

...; On 10/12/20 4:46 AM, Vjaceslavs Klimovs wrote: >> On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: >> internal error: Failed to reserve port" error is received and >> migration does not succeed: >> >> virsh # migrate cartridge qemu+tls://ratchet.lan/system --live >> --persistent --undefinesource --copy-storage-all --verbose >> error: internal error: Failed to reserve port 49153 >> >> virsh # >> > > Sorry for not replying earlier. But this is a clear libvirt bug and I > think it's a regression in...

In the notes for 2.3.0 it says that IceCast can function as a RealAudio/Helix server. Does this mean that it does the quality negotiation as well, ratcheting the bitrate up and down if it needs to? Or am I reading this all wrong? Thanks. -- //// Jason M. SULLIVAN jsullivan@nc.rr.com |c-oo http://www.jason0x21.org \_- "That's not music, that's just sound!" - J. David Fries

I would be grateful if someone could tell me where to find the docs to get started on the following problem: A program needs to be written to place a SIP call to a certain extension on another Asterisk system, and see whether the call state ratchets up to "ringing", then drop, and take action on the results. Can anyone refer me to the appropriate starting point to read up on this? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/2009...

...ith native NBD live migration w/ TLS and have a couple of questions. 1) It appears that in some cases modified default_tls_x509_cert_dir from qemu.conf is not respected, seems like virsh always expects a default location and does not check default_tls_x509_cert_dir: virsh # migrate vm1 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --verbose --tls error: internal error: unable to execute QEMU command 'object-add': Unable to access credentials /etc/pki/qemu/ca-cert.pem: No such file or directory It's checking /etc/pki and not the location specified...

...terprise users of GNURadio are going to need the latest version regardless of the packaging and versioning guidelines. Or, in summary, stability should not be equated with version stagnation, IMHO. As always, I reserve the right to be wrong, etc. And maybe it is time to get back on the Fedora ratchet on the workstation; not something I'm looking forward to. At least the Fedora ratchet steps are smaller than the EL steps, even if they are closer together. Software Collections helps a great deal, especially in the server space, but there is just way too much inflexibility in some of the...

...dhat.com> wrote: > > On Sat, Aug 15, 2020 at 15:38:19 -0700, Vjaceslavs Klimovs wrote: > > Hey all, > > With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in > > tunneled mode does not work for me: > > > > virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live > > --persistent --undefinesource --copy-storage-all --tunneled --p2p > > error: internal error: qemu unexpectedly closed the monitor: Receiving > > block device images > > Error unknown block device > > 2020-08-15T21:21:48.995016Z qemu-system-x86_64:...

...ting something that samba should recognize as an ADS that is arbitrarily large. If I run the following powershell command from a Windows client "Get-Item -Path .\test.txt -stream *", I do not see the ADS listed unless it is smaller than 64KB. When it is larger than it, and I have logging ratcheted up I get logs like below. Out of curiousity, does Samba not support large ADS? Do you have any pointers on how to maybe coax Samba into letting me abuse xattrs better? [2017/08/02 10:55:51.475689, 10, pid=43437, effective(21112, 20513), real(0, 0), class=vfs] ../source3/modules/vfs_streams_xattr...

...pool based on 6 zones nov 05 03:09:02 > data.contoso.com named[2807]: Loading 'AD DNS Zone' using driver > dlopen nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: > starting configure nov 05 03:09:02 data.contoso.com named[2807]: > samba_dlz: Ignoring duplicate zone 'ratchet.com' from > 'DC=@,DC=ratchet.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=contoso,DC=com' > nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: Ignoring > duplicate zone '17.172.in-addr.arpa' from > 'DC=@,DC=17.172.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,...

...]: sizing zone task pool based on 6 zones nov 05 03:09:02 data.contoso.com named[2807]: Loading 'AD DNS Zone' using driver dlopen nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: starting configure nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: Ignoring duplicate zone 'ratchet.com' from 'DC=@,DC=ratchet.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=contoso,DC=com' nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: Ignoring duplicate zone '17.172.in-addr.arpa' from 'DC=@,DC=17.172.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=contoso,DC=com...

...pool based on 6 zones nov 05 03:09:02 > data.contoso.com named[2807]: Loading 'AD DNS Zone' using driver > dlopen nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: > starting configure nov 05 03:09:02 data.contoso.com named[2807]: > samba_dlz: Ignoring duplicate zone 'ratchet.com' from > 'DC=@,DC=ratchet.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=contoso,DC=com' > nov 05 03:09:02 data.contoso.com named[2807]: samba_dlz: Ignoring > duplicate zone '17.172.in-addr.arpa' from > 'DC=@,DC=17.172.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,...

On Sat, Aug 15, 2020 at 15:38:19 -0700, Vjaceslavs Klimovs wrote: > Hey all, > With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in > tunneled mode does not work for me: > > virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live > --persistent --undefinesource --copy-storage-all --tunneled --p2p > error: internal error: qemu unexpectedly closed the monitor: Receiving > block device images > Error unknown block device > 2020-08-15T21:21:48.995016Z qemu-system-x86_64: error while loading >...

On 10/12/20 4:46 AM, Vjaceslavs Klimovs wrote: > On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: > internal error: Failed to reserve port" error is received and > migration does not succeed: > > virsh # migrate cartridge qemu+tls://ratchet.lan/system --live > --persistent --undefinesource --copy-storage-all --verbose > error: internal error: Failed to reserve port 49153 > > virsh # > Sorry for not replying earlier. But this is a clear libvirt bug and I think it's a regression introduced by the following commit:...

...should recognize as an ADS that is > arbitrarily large. > > If I run the following powershell command from a Windows client "Get-Item > -Path .\test.txt -stream *", I do not see the ADS listed unless it is > smaller than 64KB. When it is larger than it, and I have logging ratcheted > up I get logs like below. Out of curiousity, does Samba not support large > ADS? Do you have any pointers on how to maybe coax Samba into letting me > abuse xattrs better? Yeah, iirc a built in buffer-size limit. We don't expect xattrs to be much larger, as no fs on Linux supports...

...when I reflash an 'M'? * CallVantage only allows one FXS port, however I think all the connections are there. If I flash the SIP firmware, will the other ports become enabled? Or have they been physically disabled and I can't see where they have been cut. Thanks in advance. -- Black Ratchet blackratchet <at> blackratchet.org - http://www.blackratchet.org (914) 239-5132 x8888

Hello, ? I'm trying to configure my system such that I have a TCP port listening which will send all data it receives to a serial port. ie:?? tcp/2112? -->? /dev/ttyS0 My goal would be to be able to: Use netcat to create the listen and redirect to a serial port: ? $ nc -l 2112 > /dev/ttyS0 Then in another window, run minicom at /dev/ttyS0 Then in a 3rd window, ? $ telnet localhost

...S and have > a couple of questions. > > 1) It appears that in some cases modified default_tls_x509_cert_dir > from qemu.conf is not respected, seems like virsh always expects a > default location and does not check default_tls_x509_cert_dir: > > virsh # migrate vm1 qemu+tls://ratchet.lan/system --live --persistent > --undefinesource --copy-storage-all --verbose --tls > error: internal error: unable to execute QEMU command 'object-add': > Unable to access credentials /etc/pki/qemu/ca-cert.pem: No such file > or directory > > It's checking /etc/pki...

Hello, My server with CentOS 6.8 just failed PCI scan, so I'm looking into vulnerable packages. PHP 5.3.3 have multiple vulnerabilities, some of them are fixed/patched or have some kind of workaround. But I can't find a way to fix this one. Red Hat state: under investigation. https://access.redhat.com/security/cve/cve-2016-4073 This CVE is 6 months old, and it doesn't look like it