I have a problem and I can't find how to solve it so if anybody can give me a hand I will be gratefull.
After upgrading one of my proxmox vm to debian 8 jessie all worked fine, but when I have restarted the vm doen't load.
I have connected through the VNC of Proxmox and shows this when booting and I can't type or do anything.
systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVININT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
Detected virtualization 'openvz'.
Detected architecture 'x86-64'.
Welcome to Debian GNU/Linux 8 (jessie)!
Sethostname to <srv4>.
Failed to enable kbrequest handling: Invalid argument
Cannot add dependency job for unit rpcbind.service, ignoring: Unit rpcbind.service failed to load: No such file or directory.
Cannot add dependency job for unit display-manger.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Assertion 'clock_gettime(clock_id, &ts) == 0' failed at ../srv/shared/time-util.c:33, function no(). Aborting.
Caught <ABRT>, dumped core as pid 53.
Freezing execution.
Anybody knows what it's happening?
Thanks for your support.
now I know what has happened.
I installed a new virtual machine (openVZ containter) (CT) with debian 8 and had the same problem at start, I thought that the problem was with the upgrade but having the same problem with a new fresh debian 8 install I have search for new solutions.
The problem it's that I was running Proxmox 3.2 which uses a linux Kernel not compatible with Debian 8.
https://forum.proxmox.com/threads/debian-8.22043/
So be adviced, if you are using Proxmox 3.x don't upgrade your CT's to Debian 8 jessie or your machines will never restart.
Important, after the upgrade all works perfectly until you restart, I was working with Debian 8 for more than one month after the upgrade with any issues, until I needed to restart.
Best!
Related
I have a fresh install of 18.04 SERVER installed on an Advantech SBC. 16.04 Server was working find but on 18.04 Server when I do a:
sudo shutdown -r now
The system starts the shutdown but stops with the last status line:
[ OK ] Stopped LVM2 metadata daemon.
I've tried some different bios configurations with power management but I can't seem to get it to restart. Only option at that point is to physically kill power and power up.
Anyone seen this? Any ideas on what to try?
On my SBC setting the South Bridge USB Configuration for Windows 8.x compatibility resolved this issue. Seems that the V4.15 kernel interactions with hardware are different enough to have caused this problem.
Issue
when vagrant up it says "It appears your machine doesn't support NFS"
Setups
Debian GNU/Linux 8 (jessie）
Vagrant 1:2.0.0
Virtualbox 5.1.30 r118389
Detail
After using apt-get to update and upgrade the system, I basically followed the instruction from the Mediawiki page, since I wanted to install Mathoid to render LaTeX equations locally for mediawiki page.
However, when I vagrant up it echos the following:
It appears your machine doesn't support NFS, or there is not an
adapter to enable NFS on this machine for Vagrant. Please verify
that `nfsd` is installed on your machine, and try again. If you're
on Windows, NFS isn't supported. If the problem persists, please
contact Vagrant support.
I checked if nfsd is correctly working on the host, and it says it's enabled.
# /etc/init.d/nfs-kernel-server status
nfs-kernel-server.service - LSB: Kernel NFS server support
Loaded: loaded (/etc/init.d/nfs-kernel-server)
Active: active (running) since Sun 2017-10-15 07:56:32 -02; 2 weeks 0 days ago
CGroup: /system.slice/nfs-kernel-server.service
??1277 /usr/sbin/rpc.mountd --manage-gids
I also tried google, and did not find a solution that fits my problem and I couldn't find any hint to resolve this. For instance, I tried to install the package
sudo apt-get install nfs-common
But it has been already installed.
Thank you in advance.
The command mentioned below works for linux mint 18.3:
sudo apt-get install nfs-common nfs-kernel-server
For Windows users seeing that error, run the following command to add support for NFS for Vagrant:
vagrant plugin install vagrant-winnfsd
The GitHub repo for this plugin is found here.
Also, to see the currently installed Vagrant plugins run this:
vagrant plugin list
Can be fixed by adding any exports to /etc/exports.
by :
modprobe nfs
modprobe nfsd
then running vagrant, which will add /etc/exports, then reloading
kernel-server and restarting vagrant.
issue http://jb-blog.readthedocs.io/en/latest/posts/0021-vagrant-nfs-problems.html
instead of installed NFS cos really no supported :
Try just removing type: nfs from the vagrant_synced_folders
More : https://www.vagrantup.com/docs/synced-folders/nfs.html
After a recent kernel update for Centos 7.4, Paravirtualized DomUs under Xen stooped booting. They just crash on boot.
Apparently it seems a new restriction in RHEL 7 kernel. And there are some suggestions i found in different forums to switch to HVM or PVHM. Problem is that most of Paravirt DomUs are installed on plain disks (without partitions). But to convert them to HVM or PVHM they need Grub installed inside the VM which need partition table. So it is a full reinstallation :(
Centos guys say it is something RHEL need to fix. So is this a bug which can be fixed in near future ? or is that RHEL just dont want its kernel to run on Paravirt vms any more ?
Had the same issue, and as a hack workaround installed the CentOS Xen kernel before upgrading to 7.4. Had no issues booting with that kernel in place. If RedHat fixes their kernel it should be relatively simple to switch back to it.
I have installed the Ubuntu in virtualbox for months.
After I upgrade the Linux kernal, I cannot boot Ubuntu with normal mode.
But it can success boot in recovery mode
I occurred some error:
floppy0: no floppy controllers found. => this will let me wait a few minutes, and it will go through.
intel_rapl: no valid rapl domains found in package 0 =>the boot process stuck at this error
I don't know whether it's a problem whit kernal 4.72 or not.
Linux kernal: 4.72 lowlatency amd64
virtualbox version: 5.14
physic cpu: x86_64
I solved the problem by myself.
Below is my method:
1.Enter recovery mode.
2.Install generic version kernel
3.Purge all of the lowlatency kernels
But I still don't know why virtualbox can't run with lowlatency version kernel.
And the error (or normal boot process),"intel_rapl: no vaild rapl domains found in package 0", is still showed when boot, but it dosen't let the boot process stop.
few months ago I got access to a VPS with installed Debian 8 Jessie.
The strange thing for me was that after perform some action (like service [stop|start|restart], debian not notify me (ex: Restarting nginx: nginx, like old debian 7 wheezy).
Yesterday, i installed on my virtual machine Debian 8 Jessie, but the "bug" persists.
Should I install something extra library, or to set up them?
Thanks in advance.
Debian uses systemd now.
systemctl start example1
Investigate why systemd hangs on startup or on reboot/shutdown.
Increase verbosity via cmdline: Add "systemd.log_target=kmsg systemd.log_level=debug"
[ /etc/default/grub ]
GRUB_CMDLINE_LINUX="systemd.log_target=kmsg systemd.log_level=debug" <--- Add here (by uncommenting you can easily switch to debug)
# update-grub
Systemd is not as verbose as the old SysV scripts, so your described "bug" is intended behaviour.
The old commands, like "service" are just simple symlinks / script which delegate the work to systemd.
As far as I know this is the same for the /etc/init.d scripts.