search for: 2b94

...nd perl v5.10.1 This is the latest update I can get for RHEL 6.8. Can you advice me the possible way to proceed with v2v? -- *Saman K. Bandara,** Database Administrator* *ShipXpres Technologies (Pvt) Ltd.* 2300 Marsh Point Road, Suite 101 || Neptune Beach, FL 32266 Phone: +94 71 8135485 <%2B94%20718135485> | +94 <%2B94%20777522730>76 6014001 *Company Website <http://www.shipxpress.com/>* || *LinkedIn <http://www.linkedin.com/company/shipxpress> *|| *Facebook <https://www.facebook.com/ShipXpressInc>* || *Twitter <https://twitter.com/ShipXpressInc>*

...rwmj.wordpress.com > virt-builder quickly builds VMs from scratch > http://libguestfs.org/virt-builder.1.html > -- *Saman K. Bandara,** Database Administrator* *ShipXpres Technologies (Pvt) Ltd.* 2300 Marsh Point Road, Suite 101 || Neptune Beach, FL 32266 Phone: +94 71 8135485 <%2B94%20718135485> | +94 <%2B94%20777522730>76 6014001 *Company Website <http://www.shipxpress.com/>* || *LinkedIn <http://www.linkedin.com/company/shipxpress> *|| *Facebook <https://www.facebook.com/ShipXpressInc>* || *Twitter <https://twitter.com/ShipXpressInc>*

...n failed: Failed to step SASL negotiation: -7 (SASL(-7): invalid parameter supplied: Unexpectedly missing a prompt result) -- *Saman K. Bandara,** Database Administrator* *ShipXpres Technologies (Pvt) Ltd.* 2300 Marsh Point Road, Suite 101 || Neptune Beach, FL 32266 Phone: +94 71 8135485 <%2B94%20718135485> | +94 <%2B94%20777522730>76 6014001 *Company Website <http://www.shipxpress.com/>* || *LinkedIn <http://www.linkedin.com/company/shipxpress> *|| *Facebook <https://www.facebook.com/ShipXpressInc>* || *Twitter <https://twitter.com/ShipXpressInc>*

...smbds also start to die. Again no pattern. No way to reproduce. But there were strange entries in the logs linux smbd[8311]: smbd/oplock.c process_local_message(418) linux smbd[8311]: process localmessage: unknown UDP message command code (e393) ignoring with different command codes i.e. 1e73, 2b94 and others. After some of these messages have arrived the smbd processes start to panic with internal errors. one after the other. I could locate the machine which is sending the UDP messages. And we will check what happens when that machine is down tomorrow. But anyway, does anyone has a clue...

...smbds also start to die. Again no pattern. No way to reproduce. But there were strange entries in the logs linux smbd[8311]: smbd/oplock.c process_local_message(418) linux smbd[8311]: process localmessage: unknown UDP message command code (e393) ignoring with different command codes i.e. 1e73, 2b94 and others. After some of these messages have arrived the smbd processes start to panic with internal errors. one after the other. I could locate the machine which is sending the UDP messages. And we will check what happens when that machine is down tomorrow. But anyway, does anyone has a clue...