Discuss

discuss@lists.centos.org

3 participants
34748 discussions

Fail to load kernel module ipmi_si on CentOS-6
by Frank Yu 28 May '16

28 May '16

Hi all, I am trying to load kernel module ipmi_si, while failed with error "No such device", truth is I can find file in ../kernel/drivers/char/ipmi/ipmi_si.ko. So why I can't load it? Steps: # ls -l /lib/modules/2.6.32-573.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko -rwxr--r--. 1 root root 93080 Jul 23 2015 /lib/modules/2.6.32-573.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/2.6.32-573.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko): No such device # lsmod |grep ipmi ipmi_devintf 7729 0 ipmi_poweroff 8532 0 ipmi_watchdog 17874 0 ipmi_msghandler 38701 3 ipmi_devintf,ipmi_poweroff,ipmi_watchdog # ipmitool Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory What should I do if I want to setup IPMI on my centos host? -- Regards Frank Yu

3 3

Systemd and VirtualBox
by Rob Kampen 28 May '16

28 May '16

The continuing challenges of getting a workable server continue. The latest spins of VirtualBox seem to have solved the issues of DKMS auto compiles of the driver being aborted. The yum updates work as expected, provided one stops the running vms manually first. However, trying to get systemd to start the vms is proving to be a PITA. I have extensively googled and found that there are no specific instructions for Fedora/Redhat/CentOS and VirtualBox setups for systemd. After many trials and errors I have this systemd service file: filename - /etc/systemd/system/vboxstarter@.service [Unit] Description=VBox Virtual Machine %i Service Requires=systemd-modules-load.service vboxballoonctrl-service.service After=systemd-modules-load.service vboxballoonctrl-service.service Conflicts=shutdown.target [Service] User=<username> Group=vboxusers Restart=on-failure TimeoutSec=5min Environment="VBOX_USER_HOME=/home/rkampen/VirtualBox VMs/%i" ExecStart=/usr/bin/VBoxHeadless -s %i ExecStop=/usr/bin/VBoxManage controlvm %i savestate [Install] WantedBy=multi-user.target and on occasions the invocation systemctl start vboxvmstarter(a)Windoze10_2.service will work, although recently it is failing always with >$ systemctl status vboxvmstarter(a)Windoze10_2.service ● vboxvmstarter(a)Windoze10_2.service - VBox Virtual Machine Windoze10_2 Service Loaded: loaded (/etc/systemd/system/vboxvmstarter@.service; enabled; vendor preset: disabled) Active: deactivating (stop-sigterm) (Result: exit-code) since Tue 2016-05-17 03:25:02 EDT; 4s ago Process: 1987 ExecStop=/usr/bin/VBoxManage controlvm %i savestate (code=exited, status=1/FAILURE) Process: 1906 ExecStart=/usr/bin/VBoxHeadless -s %i (code=exited, status=1/FAILURE) Main PID: 1906 (code=exited, status=1/FAILURE) CGroup: /system.slice/system-vboxvmstarter.slice/vboxvmstarter(a)Windoze10_2.service └─1940 /usr/lib/virtualbox/VBoxSVC --auto-shutdown May 17 03:25:02 media.pcol.org systemd[1]: Started VBox Virtual Machine Windoze10_2 Service. May 17 03:25:02 media.pcol.org systemd[1]: Starting VBox Virtual Machine Windoze10_2 Service... May 17 03:25:02 media.pcol.org systemd[1]: vboxvmstarter(a)Windoze10_2.service: main process exited, code=exited, status=1/FAILURE May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Could not find a registered machine named 'Windoze10_2' May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), com...pports May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.a...VM.cpp May 17 03:25:02 media.pcol.org systemd[1]: vboxvmstarter(a)Windoze10_2.service: control process exited, code=exited status=1 Hint: Some lines were ellipsized, use -l to show in full. as <username> a vboxmanage list vms "Windoze10_2" {51c8f956-9aba-4d2a-942c-8f46889d5bc0} shows the required vm. as root or using sudo it returns nothing. thus my only conclusion is that systemd actually runs this as root and ignores the User= line of the [Service] stanza. No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working. Or any systemd gurus that can point me at the specific foo required to beat this deamon into submission. TIA Rob P.S. I deliberately set up the VirtualBox vms under a non privileged user account. I have tried setting up a symbolic link from /root to the ~/username/VirtualBox\ VMs folder and made root a member of the virtualboxusers group - no difference, as expected, but getting desperate.

14 26

Continuous Release repository RPMs now released
by Johnny Hughes 28 May '16

28 May '16

The Continuous Release repository RPMs for CentOS-6.8 are now released. It includes the following releases: https://lists.centos.org/pipermail/centos-cr-announce/2016-May/thread.html Specifically, there are following Security Updates included: CESA-2016:0996 Important CentOS 6 openssl Security Update CESA-2016:0997 Important CentOS 6 qemu-kvm Security Update CESA-2016:1041 Important CentOS 6 thunderbird Security Update CESA-2016:0760 Moderate CentOS 6 file Security Update CESA-2016:0778 Moderate CentOS 6 icedtea-web Security Update CESA-2016:0855 Moderate CentOS 6 kernel Security Update CESA-2016:0780 Moderate CentOS 6 ntp Security Update CESA-2016:0741 Moderate CentOS 6 openssh Security Update As well as more than 300 other bug fix updates. Please read the CentOS-6.8 Release Notes: https://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.8 As well as the RHEL-6.8 release notes and technical notes (since CentOS-6.8 is based on the RHEL-6.8 source code): Release Notes: http://red.ht/1WBF3u4 Technical Notes: http://red.ht/1YwcEDI If you do not want to install the CR repository, the full 6.8 release should happen around 10-21 days from today. For more information on the CR repository, see this link: https://wiki.centos.org/AdditionalResources/Repositories/CR Thanks, Johnny Hughes

3 4

Re: [CentOS] ipmitool and CentOS 7
by m.roth＠5-cent.us 28 May '16

28 May '16

---------------------------- Original Message ---------------------------- Subject: ipmitool and CentOS 7 From: m.roth(a)5-cent.us Date: Mon, May 16, 2016 16:57 To: "CentOS" <centos(a)centos.org> -------------------------------------------------------------------------- On Dells running CentOS 6, we could use this command ipmitool delloem lcd set mode userdefined "$(uname -n | sed -e 's/\..*//' )" to set the little LCD screen to display the system name, In the latest sevens, it fails, and gives me usage for the command... which displays exactly that syntax. Anyone have a clue? --------------------------- Following myself up: it worked 100% of the time on CentOS 7 on dells. On CentOS 7, the whole set of delloem appear to fail. For example, ipmitool delloem lcd info produces "LCD info", rather than the service tag that it comes from Dell displaying. All variants I try to set it produce a list of usage options for ipmitool delloem lcd. I'm starting to think that the delloem is broken; either it's ipmitool, or A side note, for the person who suggested uname -s - that produces Linux. -n produces the FQDN. mark

3 2

Re: [CentOS] dnf replacing yum?
by James B. Byrne 27 May '16

27 May '16

On Thu, May 26, 2016 10:51, Juan Bernhard wrote: > > El 26/05/2016 a las 11:39 a.m., Valeri Galtsev escribió: >> I guess, it is just me in general unhappy about all Linuxes >> getting much less "UNIX"y lately. > > I feel you Valerei, im switching new server instalations to FreeBSD. > Im tired to spend useful time learning new ways (systemd, firewalld, > dnf, etc) to do the same old sh*t. > > We are doing exactly the same thing and for the same reasons. We have been running RH or its derivatives since 1998 but now it is time for us to move on. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Redefine ethX interface names in CentOS 5.11?
by Nicolas Kovacs 27 May '16

27 May '16

Hi, I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd like to swap the interface names, but I don't know how to go about that under CentOS. Here's what I would do on a Slackware server (I have one next to me in my office). Open /etc/udev/rules.d/70-persistent-net.rules and edit it: # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:04.0/0000:03:00.0 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:64:8a:4c:c2", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="2c:27:d7:15:54:a1", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" To swap interfaces, I simply have to switch the respective NAME="ethX" attributes and restart the server. How would you do something similar on a machine running CentOS 5.11? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Re: [CentOS] [SOLVED] Kernel panic on 6.8 release with kernel-2.6.32-642.el6.x86_64
by Sorin Srbu 27 May '16

27 May '16

> -----Original Message----- > From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf Of Sorin Srbu > Sent: den 27 maj 2016 07:43 > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32- > 642.el6.x86_64 > > > > Uninstalled NFS, as it wasn't needed anyway. > > > > > > Still got the panic. > > > > Seriously, what panic? > > The one I posted a screen dump of earlier. Did some more digging this morning. All physical machines are quite okay with the 6.8 upgrade. All virtual machines running on Hyper-V get a kernel panic - if the linux integration services (lis) are installed on the guest. Uninstalling lis, then applying the kernel-2.6.32-642.el6.x86_64 and rebooting works just fine. No kernel panics. Supposedly (according to some forum posts I read) the lis shouldn't care what kernel is actually running, as long as it is compiled with a kernel that is installed and available on the system, in this case the last previous before the 6.8-upgrade. In any case, problem solved for now. Thanks for all the feedback! Marking thread as solved. -- //Sorin

1 0

Recommendations for Infiniband with CentOS 6.7
by Pat Haley 27 May '16

27 May '16

Hi All, We looking for suggestions on dealing with mellanox drivers in CentOS 6.7 We tried installing mellanox drivers (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64) on a Quanta Cirrascale server running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64. When we rebooted the machine after installing the drivers, it went into a kernel panic for every installed kernel except for Centos 6.7 2.6.32-573.22.1.el6.x86_64.debug. After we uninstalled the drivers, the machine failed to boot for any installed kernel. Any suggestions on how to proceed would be greatly appreciated. Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

4 6

centos7 tmpfiles.d deleted outdate files
by Qiang Chen 26 May '16

26 May '16

Hi all, I use centos7 and don't want to use tmpwatch as well as crond. I have a question to use `systemd-tmpfiles-clean.service` with my custom configured file in `tmpfiles.d` to delete outdated files periodically in some log dir. I have a `tmpfiles.d` configured file in `/etc/tmpfiles.d` named `my_log.conf` in following contents. ``` #Type Path Mode UID GID Age Arg r /chenqiang 0775 root root 10s r /chenqiang/test_10s r /chenqiang/test_20s ``` If I run `systemd-tmpfiles --remove` with above configure, all files and dir will be deleted if I set 'r' type for the files and dir. but, I want to only delete some outdated files in the dir. and I use `systemd-tmpfiles --clean` with following configure. ``` #Type Path Mode UID GID Age Arg d /chenqiang 0775 root root 10s f /chenqiang/test_10s 0660 root root 10s f /chenqiang/test_20s 0660 root root 20s ``` It can delete dir if the age > 10s, but can't delete the files in it. So, would some one help me if I want to delete the outdated files ? -- Best Regards, Chen, Qiang

3 3

Re: [CentOS] dnf replacing yum?
by Timothy Murphy 26 May '16

26 May '16

Kenneth Porter wrote: > I saw mention of dnf in a blog article about installing a package on > CentOS. Further investigation revealed that Fedora is replacing yum with > dnf, apparently a new and better yum. But it wasn't clear if dnf was a For the normal user (like me) dnf is neither better nor worse than yum. In fact it is almost identical. In my view, the introduction of a new name was completely unnecessary and the cause of the only (small) complication with the changeover, eg should I look in /etc/yum.repos.d/ or /etc/dnf.repos.d/ ? Also, yum had associations which it was sad to lose. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

9 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss