similar to: installing xen on a vmware work station

Hi, I recently compiled a Xen-4.0.1 and pv-ops Dom0 2.6.32.27 kernel from JF''s tree.Where my hypervisor could not boot and unfortunately the system is rebooting so frequently that I am not able to note down the error messages on a paper and pencil.So now I am planning to go for a non pv-ops Dom0.I am not clear as what should be the approach? I have been Googling it every now and then and

Following is one grub entry menuentry "Ubuntu, Linux 2.6.32.27" { insmod ntfs set root=''(hd0,2)'' search --no-floppy --fs-uuid --set 96f65c80f65c6313 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) linux /boot/vmlinuz-2.6.32.27 root=/dev/sda2 loop=/ubuntu/disks/root.disk ro quiet splash initrd

I have a Centos 7 install that seems to be filling up disk space to 100% on the root partition. in /tmp I found files of names... systemd-private-XXXXXXXX-colord and rtkit I have never seen these files before. there were also files of XXXXXXXXXXXXX.tmp in the /tmp folder. Why are these files appearing? I have a number of installs and never came across this before. Thanks, Jerry

Attempting to lookup why rsyslogd is listening on the high port UDP/51427. Have not succeeded in what this port is used for and what directive controls what interface it binds to. [root at bedrock ~]# netstat --listen --inet --program --numeric | grep syslog udp??0??0 0.0.0.0:51427??0.0.0.0:*???66655/rsyslogd? -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383

Include logs from the failed boot On Jun 11, 2015 10:55 PM, "Andre Campos Rodovalho" < andre.rodovalho at gmail.com> wrote: > Hello, I'm facing issues with a Point of View GT210/218 and nouveau > drivers. I'm using ubuntu server with LXDE on top of it... > > *lshw -c video* output: > *-display > description: VGA compatible controller >

https://bugs.freedesktop.org/show_bug.cgi?id=68572 Priority: medium Bug ID: 68572 Assignee: nouveau at lists.freedesktop.org Summary: shutdown threshold temperature sometimes isn't restored properly after hibernate QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

On Thu, 2017-08-17 at 16:01 -0400, Jerry Geis wrote: > This is a listing. > > total 44 > drwx------ 2 root root 6 Aug 17 15:36 lu26465gujqup.tmp > drwx------ 2 root root 8192 Aug 17 15:37 lu27063gukci0.tmp > drwx------ 2 root root 8192 Aug 17 15:43 lu3205guot5q.tmp > drwx------ 2 root root 8192 Aug 17 15:48 lu4177guts1n.tmp > drwx------ 2 root

centos 6.4, setup to be syslog server. Doing remote syslog using tcp works fine, so now want to add relp. I installed the rsyslog-relp package and told rsyslog.conf to use it: # RELP Syslog Server: $ModLoad imrelp # provides RELP syslog reception $InputRELPServerRun 20514 when I restart rsyslog I am told it does not like my InputRELPServerRun line: Oct 28 13:43:54 scan rsyslogd: [origin

Hi, My rsyslog is not working as expected. I have some thing in rsyslog.d that do well, like this: # Log all iptables stuff separately :msg, contains, "iptables: " { action(type="omfile" file="/var/log/iptraf/info") } No problems with that. Bu what's in /etc/rsyslog.conf like: mail.* /var/log/mail/info don't do anything at all. Rsyslogd -N1 is OK,

Dear All I am using a centos server for cdr billing and mediation device on a remote network. I am experiencing problem that I am suspicious it comes from main supply power cut at the remote site. The power supply to the remote site comes from battery charger that will be automatically switched in circuit under main supply power cut but cannot provide adequate power for more than 2 hours . I am

Package: logcheck-database Version: 1.2.63 Severity: normal --- Please enter the report below this line. --- In fact, there does not appear to be any consideration of rsyslogd's behavior. Attached is a rule to ignore restarts. --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 990 testing ftp.debian.org 600 unstable

Hi there, I am slightly confused by the RHEL release notes and an earlier thread here about rsyslogd, so I hope someone can clear this up for me; I see that rsyslog is included in RHEL as of 5.2 (and so will be available in CentOS when 5.2 is ready) however there is no indication of whether it has been made the default syslogger or not - is it an optional package or installed by default on a

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

I have several recently-installed CentOS 7 servers that keep having systemd-journald corruption (which stops ALL logging, including syslog). Interestingly, they are all spam-scanning servers running amavisd-new (so could be some particular pattern is triggering it). Is there a "supported" way to just cut systemd-journald out of the picture and have log entries go straight to rsyslogd?

In case anyone is interested, I found the problem. I was running samba in a container that did not have any syslog service (rsyslogd or syslog-ng) running. By default, samba syslog only sends messages to the system's syslog socket and there was nothing listening on it so the messages just got dropped. I put rsyslogd in the container and configured it to listen on the syslog socket and am

Folks I'm sure the Centos team has done a yeoman's job getting Centos7 ready, and that the Redhat team has done marvels in creating rhel7, but here's a little voice from a personal hobbyist user. Background: ('ve been maintaining several remote servers since Redhat 6 days, migrating from that to Whitebox, then Centos, and things have been running as expected including the

Package: logcheck-database Severity: wishlist Tags: patch Hi, ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ kernel: imklog 3\.18\.6, log source = /proc/kmsg started\.$ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" swVersion="3.18.6" x-pid="[[:digit:]]+" x-info="http://www.rsyslog.com"\] restart$ Hendrik -- Hendrik Jaeger

Hello everyone, We have some chrooted sftp-only users on a CentOS release 6.6 server. The server had been logging their actions, but after recent updates the logs have stopped. The server correctly logs non-chrooted users: Sep 14 17:47:24 vsecure4 sshd[1981]: Accepted publickey for jcours from 192.168.10.166 port 42545 ssh2 Sep 14 17:47:24 vsecure4 sshd[1981]: pam_unix(sshd:session):

Hi folks, I came across this issue on both stock CentOS(v6.4) and Ubuntu(14.04 LTS) and was wondering if any of you have seen it. As far as I can tell this seems like a day-1 bug to me. PROBLEM: If I expire a linux user's password (passwd -e <user>) and then log in via ssh, it will prompt you for a password change. On changing the password successfully, sshd will drop the connection

Hi all, Somebody knows how can I bind rsyslogd to a specific ip adress?? I have two different interfaces on a centos5.5 host and I need to bind rsyslog to only one. Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com