hangs. Looks like
it has something to do with 8021q module.
All Xen domU's with NATed networks are reachable.
-- System Information:
Debian Release: 5.0.7
--
Regards,
Peter Viskup
Dec 14 21:25:17 server2 kernel: [1480447.233563] general protection fault:
[1] SMP
Dec 14 21:25:17 server2
different on hardware
- server1 is Xeon 3210 based with all Intel Ethernet cards
- server2 is Opteron 2431 based with Broadcom Ethernet cards
--
Peter Viskup
Dec 5 23:10:31 server1 kernel: [350429.816318] BUG: unable to handle kernel
paging request at 004817f0
Dec 5 23:10:31
to this backports kernel will
help - just before I will install it. I am running production servers
and cannot just test that.
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
the domU from the pty (ssh) console.
Both dom0 and domU were running same kernel version.
--
Peter Viskup
Dec 13 16:29:04 tis kernel: [83118.676876] BUG: unable to handle kernel NULL
pointer dereference at
Dec 13 16:29:04 tis kernel: [83118.676898] IP: [8038d104
On 12/15/2010 03:13 AM, Ben Hutchings wrote:
Do you create or modify VLAN devices when creating a new domain?
No I don't create nor modify VLAN interfaces. I just add them to the
bridge named 'xenin'. My config is like this:
# bond over cross-cabling
auto bond1
iface bond1 inet static
from VG named 'data' to my vhosts.
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
:
Debian Release: 5.0.6
--
Regards,
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hello,
there is no need to submit root privileges for this ejabberd Munin plugin.
On jabber.sk server we are running it with privileges of 'ejabberd' user
only. We are not experiencing any lack of permissions.
This should be enough:
[ejabberd_*]
user ejabberd
Best regards,
Peter Viskup
/partitions
major minor #blocks name
8 11572864 sda1
8 2 524288 sda2
8 31048576 sda3
8 41048576 sda4
8 5 524288 sda5
8 62097152 sda6
8175242880 sdb1
Best regards,
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
I am experiencing the same issue with warning message shown. Fortunately
the hibernation is working for me including the lzo compression.
Hibernation started from gnome3 session on Debian Wheezy.
Best regards,
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
cc_compile_domain : deneb.enyo.de
cc_compile_date: Thu Jun 21 06:41:09 UTC 2012
xend_config_format : 4
Regards,
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I would appreciate to have the fix ASAP.
Could somebody update this bug report with date when it is expected to
commit fix for this issue?
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
://lists.xen.org/archives/html/xen-users/2012-11/msg00111.html
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
for this on the internet.
Based on information got from Bastian it was fixed in
xen-utils-common/4.1.0~rc6-1 - means it's not fixed in Squeeze branch.
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
outputs.
[1] http://lists.xen.org/archives/html/xen-users/2012-11/msg00104.html
Best regards,
--
Peter Viskup
(XEN) Xen version 4.0.1 (Debian 4.0.1-5.4) (ultrot...@debian.org) (gcc version
4.4.5 (Debian 4.4.5-8) ) Sat Sep 8 19:15:46 UTC 2012
(XEN) Bootloader: GRUB 1.98+20100804-14+squeeze1
(XEN
On 11/21/2012 09:38 AM, Ian Campbell wrote:
On Wed, 2012-11-21 at 00:32 +0100, Peter Viskup wrote:
dom0 is booting linux-image-2.6.32-5-xen-amd64 and Debian's Xen 4.0.1 is
installed on the system.
There is long discussion [1] on the xen-users mailing list with no root
cause found.
I'm afraid
On 11/21/2012 01:11 PM, Ben Hutchings wrote:
On Wed, 2012-11-21 at 12:47 +0100, Peter Viskup wrote:
On 11/21/2012 09:38 AM, Ian Campbell wrote:
On Wed, 2012-11-21 at 00:32 +0100, Peter Viskup wrote:
dom0 is booting linux-image-2.6.32-5-xen-amd64 and Debian's Xen 4.0.1 is
installed
/debian_version
wheezy/sid
root@viskup:~# uname -a
Linux viskup 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
Best regards,
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hello Jonathan,
unfortunately I upgraded that server to Squeeze already.
The good news is that on Squeeze I already used xm block-attach many
times without any issue.
I have one last box with Lenny with some production systems, but cannot
test that on this box.
Best regards,
--
Peter Viskup
sp 7f4046cad970 error 6 in
libpthread-2.17.so[7f4060e1b000+17000]
Firefox is used as browser. No issue experienced once switching to gnash
or spark.
Once the issue occur the XDM logon window is shown and all previously
running applications are gone.
--
Peter Viskup
--
To UNSUBSCRIBE, email
consider if it is related to kernel or not.
Anyway - we just jump into situation where no dynamic domU's
configuration change is possible and this is causing us serious
manageability and serviceability issues.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683170
Best regards,
--
Peter
regards,
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
. The upgrade of Debian to testing (Wheezy) make it work.
Unfortunately didn't test the PyICQt under Wheezy - but that could solve
this issue.
[1] spectrum.im
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: libpurple0
Version: 2.7.3-1+squeeze3
After installation of Spectrum [1] on Debian Squeeze the connection to
ICQ network was not possible. Upgrade to Wheezy (libpurple0 = 2.10.6-3)
helped to solve this issue.
[1] spectrum.im
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs
changes needed, start of the
gnome-control-center is enough.
--
Peter Viskup
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 11/28/2012 12:24 AM, Peter Viskup wrote:
Test if it is working for wheezy at least and let us know.
I just found email [1] from Alexandre where he stated he tested the
Wheezy version already and it is working.
My issues with backported kernel could be related to hypervisor version
4.0
quality of rsyslog packaging.
Best regards,
--
Peter Viskup
to related configuration parameters should be made.
--
Peter Viskup
handling.
Review https://bugzilla.redhat.com/show_bug.cgi?id=848852 for reference.
The patch has been implemented already, but causing some performance issues
unfortunately. Would be good to review the code and include it in the
updates.
--
Peter Viskup
We are going to build our own packages directly from sources and thus not
sure whether I will be able to test.
On Thu, Apr 9, 2015 at 3:25 PM, Michael Biebl bi...@debian.org wrote:
Hi Peter,
Am 15.12.2014 um 11:05 schrieb Peter Viskup:
Package: rsyslog
Version: 5.8.11-3
Severity
NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Nov 27 15:33:31 2015 from jump
user1.ipa@server:~$ id
uid=73800020(user1.ipa) gid=73800020(user1.ipa)
groups=73800020(user1.ipa),73800017(group.ipa)
--
Peter Viskup
://git.fedorahosted.org/cgit/sssd.git/commit/?id=3937736546e2a4b758fded3efdff9ae690fc
Thank you for dealing with this bug report.
--
Peter Viskup
Another side-effect of use of /lib/systemd/system/suricata.service is the
options from /etc/default/suricata are not effective.
For example SURCONF of IFACE options.
The kill commands from service file are not called with $PID causing them
to fail.
ExecReload=/bin/kill -HUP $MAINPID
ExecStop=/bin/kill $MAINPID
These commands causing following errors logged to syslog (due to missing
argument):
Sep 29 14:03:20 suricata-s systemd[1]: suricata.service: main
ad-rules ; /bin/kill -HUP $MAINPID
# /usr/bin/suricatasc -c reload-rules
Unable to connect to socket /var/run//suricata-command.socket: [Errno 2] No
such file or directory
Once the /var/run/suricata will took place, it would be best to move PID
file to that directory.
--
Peter Viskup
ull
ProtectHome=true
[Install]
WantedBy=multi-user.target
Just another minor remark - sysvinit script does not report reload action
as available:
root@ba-suricata-s:~# /etc/init.d/suricata
OK
Usage: /etc/init.d/suricata {start|stop|restart|status}
--
Peter Viskup
>
> I feel we have been discussing several mixed things in this bugreport.
> Perhaps it makes sense closing this and moving to other dedicated bugs.
> What do you think?
>
Agree.
Dear all,
we run Suricata under suri user.
In bug report #839146 [1] there are comments what changes were needed on
systemd.service file to get it working properly on our Debian Jessie
systems.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839146
--
Peter Viskup
lse
id_provider = ldap
sudo_provider = ldap
ipa_server = ipa.DOMAIN
ldap_uri = ldap://ipa.DOMAIN:389
ldap_search_base = dc=domain
ldap_group_search_base = cn=groups,cn=compat,dc=domain
auth_provider = krb5
chpass_provider = krb5
krb5_kdcip = ipa.DOMAIN
krb5_server = ipa.DOMAIN
krb5_store_password_if_offline =
You can close this bug report.
Discovered the configuration option "enumerate = true" for domain
solved the issue.
It is related to LDAP schema rfc2307 (default), which support ldap
group membership relation by memberUID attribute of group. In that
case the enumeration needs to be enabled to get
We do experience the same issue running the latest version from
backports (8.23.0-2~bpo8+1).
Rsyslog without TLS is stable, with TLS we are getting hang on higher
amount of messages (120.000.000 per day, not sure about the peak value
during the hang).
Process stucked in sleep state - consuming
Still experiencing the issue.
Just reported this issue to mainstream.
https://github.com/rsyslog/rsyslog/issues/1533
--
Peter
Package: rsyslog
Version: 8.4.2-1+deb8u2
Seems there is memory leak in handling of "failed" messages - those
messages which were in the action queue when the action was suspended.
More information can be seen in bug report opened at mainstream [1].
Confirmed this bug is not recognized on rsyslog
Package: siege
Version: 4.0.2-1.1+b1
When running siege, always getting the segfault after more than 700
connections were made. Tests made on nonTLS connections with GET method
only (Debian repository URIs). Siege just stops receiving data. There are
seen high receive queues on siege side and
Please close it.
Users reporting the same under
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649106
Peter
Package: ipvsadm
Version: 1:1.28-3+b1
When invoking /etc/init.d/ipvsadm with appropriate
/etc/default/ipvsadm configuration, the sync daemons are not started.
Following errors are printed
Jan 03 16:07:24 server ipvsadm[31118]: Starting IPVS Connection
Synchronization Daemon: masterTry
Package: linux-latest
Version: 4.9.110-3+deb9u4
Severity: important
After kernel update on Debian9 system from 4.9.65-3+deb9u1 to
4.9.110-3+deb9u4 the fcheck cron job run +45000 seconds instead of
original +8500 seconds (tested twice with same results).
Tested with command
$ perf stat -B -o
Package: rsyslog
Would it be possible to provide ossl rsyslog netstream driver as an package?
It is missing and would be great to have possibilities to choose between
two TLS drivers available (GnuTLS and OpenSSL).
Tried to build the package version 8.1901 for Stretch with no issues.
$ dpkg -c
@Michael, would it make sense to build the rsyslog-ossl and place it in
non-free [1]?
Just to make it available for those who would like to use or test it.
[1]
https://www.debian.org/doc/debian-policy/ch-archive.html#the-non-free-archive-area
--
Peter
On Sat, Jun 22, 2019 at 8:50 AM Michael
Package: linux-image-amd64
Version: 4.19+105
During logrotation of files residing on NFS share the NFS client report
error "nfs4_reclaim_open_state: unhandled error -521".
After that all the listings of the directory were hanging on IO. Only the
subdirectory is affected, files and other
Package: rsyslog
Version: 8.1901.0-1
Experiencing bug with continuously restarting omfile threads and
opening/closing the files many times per second.
Restarting the rsyslog solve the issue which reoccur again on ?logrotation?
(not proved).
root@fwd01:~# date; pstree -t -sap 9276
Tue 05 May 2020
The problem is related to the threads which are stopped once the
dynaFileCache entry is invalidated.
Increasing the size of dynaFileCache solved the issue. The closed files and
stopped threads are not seen anymore.
Maybe the documentation should be updated that it is more clear.
Sent to
Seems this typo is from vanilla sources
http://cvs.savannah.nongnu.org/viewvc/jailkit/jailkit/py/jk_init.in?view=markup#l119
Just submit bugreport to maintainers and mentioned Debian bugreport as
backreference
https://savannah.nongnu.org/bugs/index.php?61060
Peter
Package: syslog-ng
Version: 3.28.1-2+b1
Link /etc/systemd/system/syslog.service still points
to /lib/systemd/system/rsyslog.service which does not exist after
installation syslog-ng.
The link should be processed in the "install" section
of /var/lib/dpkg/info/syslog-ng-core.preinst script too.
Package: jailkit
Version: 2.21-4
Seems there is small but crucial typo in /usr/sbin/jk_init
root@syslog1:~# diff -u /usr/sbin/jk_init.orig /usr/sbin/jk_init
--- /usr/sbin/jk_init.orig 2021-07-16 14:31:18.0 +
+++ /usr/sbin/jk_init 2021-08-18 11:43:43.951008684 +
@@ -116,7
Package: jailkit
Version: 2.21-4
Running command to create jail with random and urandom devices produce
following errors:
Creating device /chroot/dev/random
mknod: invalid major device number ‘1.03125’
Failed to create device /chroot/dev/random, this is a know problem with
python 2.1
use "ls -l
Package: login
Version: 1:4.8.1-1
The YESCRYPT method not listed in man pages of
login.defs, YESCRYPT_COST_FACTOR option should be listed in login.defs too
(same for man page).
~# grep -B10 "ENCRYPT_METHOD " /etc/login.defs
#
# If set to MD5 , MD5-based algorithm will be used for encrypting
57 matches
Mail list logo