On 21/01/07 03:56 PM, Jan Wagner wrote:
> On Thursday 12 October 2006 16:40, Alexey Bestchekov wrote:
>> ex:
>> [EMAIL PROTECTED] ~>/usr/lib/nagios/plugins/check_jabber -H localhost -p
>> 5223 -w 1
>> -c 2 JABBER WARNING - 0,007 second response time on port
>> 5223|time=0,007033s;0.0;0.0;0.0;0.0
>
On 29/01/07 10:47 PM, Thomas Guyot-Sionnest wrote:
> On 21/01/07 03:56 PM, Jan Wagner wrote:
>> Hey Guys,
>>
>> I can confirm this bug, since I'm also hit by it.
>>
>> nagios2:~# /usr/lib/nagios/plugins/check_tcp -H foobar -p 5223
>> TCP OK - 0,00
On 30/01/07 04:00 AM, Jan Wagner wrote:
> Hi Thomas,
>
> thanks for your help.
>
> # LANG=C ./check_tcp -H jabber.org -p 5223 --send=" to=\'jabber.org\' xmlns=\'jabber:client\'
> xmlns:stream=\'http://etherx.jabber.org/streams\'>\n" --expect=" version=\'1.0\'?> xmlns:stream=\'http://etherx.jabbe
On 30/01/07 04:00 AM, Jan Wagner wrote:
> Hi Thomas,
>
>>> I also see one more possible problem. Should it be CRITICAL instead of
>>> WARNING when the output doesn't match? And do you have an external
>>> jabber host to check against so I can make sure the send/expect rules
>>> are right?
>> The a
On 31/01/07 02:47 AM, Jan Wagner wrote:
> On Wednesday 31 January 2007 05:45, Thomas Guyot-Sionnest wrote:
>
> # ./check_jabber -H jabber.org -p 5222
> JABBER OK - 0,317 second response time on port 5222|
> time=0,317007s;0,00;0,00;0,00;10,00
>
> It's wo
Package: remmina
Version: 1.0.0-4
Severity: important
Tags: upstream
Dear Maintainer,
* What led up to the situation?
I have a clean install of debian Wheezy on Gnome-classic (about a month or two
old). I'm running reminna in the notif. area, I imported my reminna proviles
(~/remmina/*.remmin
Package: remmina
Version: 1.0.0-4
Severity: important
Tags: upstream
Dear Maintainer,
* What led up to the situation?
On a clean Wheezy install (installed 1-2 months ago). I imported my
remmina profiles (~/.remmina/*.remmina) to the new system and moved most
profiles to a "/Old" subdirectory
Hi,
I summited this bug twice as reportbug crashed at the end and I didn't
realized my mail logs were in /var/log/exim, so I thought the report was
lost. I did a test in between so Bug#700372 may be more complete. You
can mark this as a dupe.
Thanks
--
Thomas
--
To UNSUBSCRIBE, email to
These are the the relevant lines from .xsession-errors:
(vino-server:30126): Gdk-WARNING **: vino-server: Fatal IO error 11 (Resource
temporarily unavailable) on X server :0.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
GIOStream returned 0 bytes on an async read
Thanks
I will try it out next time I restart - the amd64 deb would be great, or
merely the commands to patch and build - I have all the build tools
already installed but I'm not very familiar with package patching and
building yet.
Thanks
--
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-
hard
Am 07.03.2013 um 20:22 schrieb Thomas Guyot-Sionnest mailto:derm...@aei.ca>>:
Thanks
I will try it out next time I restart - the amd64 deb would be great,
or merely the commands to patch and build - I have all the build tools
already installed but I'm not very familiar with packag
On 14/03/13 04:28 AM, Thomas Guyot-Sionnest wrote:
Hi Bernhard,
Give the kudos to my wife who tried plugging her headphones in the reset
button hole - I don't reboot quite often ;)
You packages fixed the issue - Remmina doesn't appear to crash anymore.
Note that on the first atte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Confirmed working on Version 3.2.73-2.
Thanks
- --
Thomas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlZccZoACgkQ6dZ+Kt5BchZFMwCgntw3JUGuN8c4hr8Sg4yXUfHd
sOcAnRCG3vpokYXFaTSKXK9WLLPspXY9
=i+Qn
-END PGP SIGNATURE-
Package: linux-image-3.2.0-4-amd64
Version: 3.2.73-1
Severity: critical
Hi,
This morning I updated my Dell D630 laptop running Debian Wheezy; upon
reboot the video got stuck on a black screen with only the mouse
visible, but not moving. Upon quick investigation it appears to be a
kworker thread g
On Tue, 10 Nov 2015 11:08:57 +0200 Apostolos wrote:
> Package: base
> Followup-For: Bug #801467
>
> I have exactly the same problem with Dmitry, and resolved it with acpi=off
>
Hi,
I just submitted Bug #805880 - then after looking at critical bugs in
wheezy I think this one could be related...
Likely the same bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801467
https://lists.debian.org/debian-user/2015/10/msg00175.html
--
Thomas
Package: dvdisaster
Version: 0.79.6-5
There is a new upstream location for this package.
The original sourceforge page,https://sourceforge.net/projects/dvdisaster/, now
hints to:
Follow dvdisaster
dvdisaster Web Site [https://dvdisaster.jcea.es/]
The leading fork of dvdisaster on Github,htt
Regarding the recv() failed, why don't you use check_tcp instead?
check_smtp isn't meant to monitor a broken SMTP server and report it as
OK; if it doesn't work anymore it may be because an actual bug was
fixed.
check_tcp will return OK is it manages to connects - you can also add
options to send
Please disregard last comment - I just realized it's about offset
calculation, not IPv6 usage.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Works for me - I tried blocking both address alternatively so that I could
see results with either peer0 or peer1 unresponsive.
what check_ntp version are you using?
--
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
This bug is invalid.
The locale also affects input data. By passing a fractional number using
a dot (0.5), the function that converts it from string to the internal C
type "double" stops reading at the first non-numeric character (dot) as
it expects commas as the decimal separator. The end result
Revision: 2008
http://nagiosplug.svn.sourceforge.net/nagiosplug/?rev=2008&view=rev
Author: dermoth
Date: 2008-05-30 16:38:00 -0700 (Fri, 30 May 2008)
Log Message:
---
Fix Debian bug #460097: check_http --max-age broken (Hilko Bengen)
Modified Paths:
--
nagiosplug/tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This fails because a threshold was specified, which was superfluous.
This is the behavior of 1.4.14 and earlier, and the reason your check
worked in 1.4.15 was a regression.
I wrote a test. Then using the test I can clearly explain check_snmp's
behavi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/01/10 06:41 PM, Jan Wagner wrote:
> Hi Matija,
>
> I just fixed #534604 but not #51458, the changelog is just wrong. But I
> pinged
> upstream about you patch, if its a valid change for all conditions ...
> Actually there is just more evaluat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for your report.
This has been fixed in nagios-plugins. The sytax is --onredirect=sticky
though. see "check_http --help"
- --
Thomas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://eni
OCTET_STR, ASN_OCTET_STR, ASN_OCTET_STR, ASN_OCTET_STR, ASN_OCTET_STR, ASN_UNSIGNED, ASN_UNSIGNED, ASN_COUNTER, ASN_COUNTER64, ASN_UNSIGNED, ASN_COUNTER, ASN_OCTET_STR, ASN_OCTET_STR, ASN_OCTET_STR, ASN_OCTET_STR );
+my @values = ($multiline, $multilin2, $multilin3, $multilin4, $multilin5, 4294965
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
New patch attached, which is merely a bundle of all patches
(cherry-picked changes from master with some conflict fixes)
The NEWS and tests (plugins/t/* and plugins/tests/*) hunks aren't
absolutely needed, but I strongly recommend applying them becaus
Hi,
Is this bug still valid? I'm getting the same errors since I upgraded to
Debian Bullseye, however Thunderbird seems to be in enforce mode by
default and so some things are just not working anymore.
Trying to open links leads to:
Nov 23 09:57:43 debian thunderbird.desktop[392093]:
[392095:392
FYI this is the fix for chrome (attached patch), but maybe I should
report to a separate bug as it covers more than TB...
I haven't looked at the gpg issue and apparmor configuration but it may
too be best fixed at a global level... Unless we only want to allow
specific applications to run gpg?
T
Package: gnome-remote-desktop
Version: 0.1.9-5
Severity: important
Dear Maintainer,
Since the update to Bullseye I've been unable to use remote desktop.
Besides an issue for multiple daemons to open a port (vino-server used
to take the next available ports when running multiple sessions), I've
al
30 matches
Mail list logo
