Debian Installation :: Dist-upgrade From Wheezy (using Systemd) To Jessie Hangs

Nov 19, 2014

I have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.

The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.

Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade

It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.

Should I disable systemd on wheezy before? This might not have been tested so much.

View 10 Replies


ADVERTISEMENT

Debian Installation :: Multiple SystemD Errors After Upgrade From Wheezy

Mar 3, 2016

Recently I upgraded my machine from wheezy to jessie.

Everything went smooth until the point that I restarted the node.

During startup I'm getting the following message which is flooding the screen:

Code: Select allsystemd-journald[296]: Failed to forward syslog message: Connection refused

After waiting a long time (the message above still continues to flood the screen), I'm being prompted with the following:

Code: Select allGive root password for maintenance (or type Control-D to continue):

If I press Ctrl+D the boot process continues and finally boots normally.

What I can do to avoid pressing Ctrl+D during the boot process?

I'm assuming that it must be a startup service which is failing but I'm unable to trace which exactly is that.

I'm attaching the full log [URL] ....

View 8 Replies View Related

Debian Installation :: Upgrade From Squeeze To Wheezy Or Jessie

Jul 28, 2015

is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.

View 2 Replies View Related

Debian Installation :: Failed Wheezy To Jessie Upgrade (cannot Boot)

Aug 13, 2014

I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:

Code:
Select allLoading, please wait...
[    6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[    7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[    8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[   18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_

The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.

In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.

I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.

View 12 Replies View Related

Debian Installation :: Broken Grub After Wheezy To Jessie Upgrade

Jun 2, 2015

I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).

After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.

I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.

I'm using MBR/BIOS not EFI.

View 3 Replies View Related

Debian Installation :: Upgrade From Wheezy To Jessie Modify Print Drivers?

Feb 9, 2016

Does upgrade from wheezy to jessie modify print drivers....

View 1 Replies View Related

Debian Configuration :: Jessie After Dist-upgrade / Password Not Working

Jul 13, 2015

updated my jessie by apt-get dist-upgrade and there was an error said there was something wrong with some database, and I needed to run some command, but after the upgrade I forgot to run the command. After I rebooted my system I found there was not any password needed for a normal user or the root. But if I change to the emergency mode, a root password is needed.

View 4 Replies View Related

Debian :: No Internet After Upgrade From Wheezy To Jessie

May 27, 2015

I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade

Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback

[code]...

I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?

View 14 Replies View Related

Debian :: Wheezy To Jessie Upgrade Will Not Boot

May 28, 2015

With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:

input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8

So, is this a NVidia issue or a sound card issue?

View 1 Replies View Related

Debian :: Dedi Server Don't Reboot After Wheezy / Jessie Upgrade

Jul 26, 2015

I have upgraded my debian server on april when Jessie came up, but I *forgot* to reboot at this time. As a new kernel* was released this week as a security update, and since my server installed it (via unattended-upgrade on security packages), I rebooted it last night. It never came back online.

I have access to a rescue boot (Ubuntu 12.04 LTS), and tried to analyse the failure (by mounting /sys /dev /proc and /boot and chrooting), but without luck so far.

As it's a dedicated server, I don't have access to the console. What I know :

No log in var/log since the failed reboot. I don't know how to have/find others logs.Previous kernel was 3.2.0-4-amd64, new is 3.16.0-4-amd64, What I tried without luck) :

Change the booting kernel, via update-grub. Tried 3.2, 3.2 with sysvinit and 3.16 rescue mode I think. I should have done it right, but without console it's hard to tell.apt-get update/apt-get upgrade/apt-get dist-upgradeadding nomodeset to kernel load in grubWhat I haven't tried :

update-initramfs, I don't really know why it would block the boot

*linux-image-3.16.0-4-amd64:amd64 3.16.7-ckt11-1+deb8u2

View 6 Replies View Related

Debian Installation :: Systemd - Automount Windows Partition / USB Devices In Jessie

May 11, 2015

There seems to be no documentation on how to automount partitions and USB devices under systemd in Jessie. (Overall, systemd entirely lacks any useful documentation or GUI configuration tools -- all very cryptic and hidden.)

I created custom files to enable automounting. I put them in /etc/systemd/system -- this may not be the right place, but it works.

Kernel note:
This does not work under the old Wheezy kernel linux-image-3.2.0-4.

To automount my Windows partition so I can access its files, I created:
/etc/systemd/system/media-windows.mount

The name of the file must match the mount point -- in this case, /media/windows

My file notes the device and file type, plus an fmask option so all the Windows files don't seem to be executable:

[Unit]
Description = windows mount to /media/windows
[Mount]
What=/dev/sda1
Where=/media/windows
Type=ntfs-3g
Options=fmask=111
[Install]
WantedBy=multi-user.target

The file ownership must be root.root. Apparently it doesn't need to be executable.

After creating, enable with:

sudo systemctl enable media-windows.mount

and it will mount on the next boot.

I read elsewhere that the before running the enable command you should run a start command:

sudo systemctl start media-windows.mount

but that didn't work for me.

View 2 Replies View Related

Debian Installation :: Suspend / Resume / Restore Services Under Systemd On Jessie

May 11, 2015

Fixing my chronic suspend/resume problems turned out to be easier under systemd, but like everything else lacks documentation.

To suspend rather than power off when pressing the power button, I edited /etc/systemd/login.conf

uncommenting this line and changing it to suspend:
HandlePowerKey=suspend

and uncommenting the line
HandleLidSwitch=suspend

Some services were lost on resume. This problem seems common. To run a command on resume, I believe you have to make your own script, and create a systemd file to run it.

My script is /home/james/.bin/james-resume.service, which contains:

#! /bin/sh
/sbin/hdparm -B 255 /dev/sda

This must be executable. Ownership doesn't seem to matter.

To run it, I made a file in /etc/systemd/systen/suspend.target.wants
The file name must match the script name:
/etc/systemd/system/suspend.target.wants/james-resume.service

This contains:

[Unit]
Description=Run James jobs at resume
After=suspend.target
After=hibernate.target
After=hybrid-sleep.target

[Service]
ExecStart=/bin/bash /home/james/.bin/james-resume.service
[Install]
WantedBy=suspend.target
WantedBy=hibernate.target
WantedBy=hybrid-sleep.target

Ownership must be root.root. Apparently it doesn't need to be executable.

Then enable with:
sudo systemctl enable james-resume.service

and check with:
sudo systemctl status james-resume.service

If it says the service is loaded, it's OK -- inactive only means it's done running.

View 7 Replies View Related

Debian Installation :: Overwrite Wheezy With Jessie

Jun 20, 2015

I already have a Notebook with windows (for some reason it needs 3 partitions..) and wheezy. When I installed wheezy I create 2 logical partition inside a primary one: one logical for /home and the other one for filesystem. Now I would like to overwrite wheezy and get get jessie, but without touching windows and home.

I already try to upgrading and it went wrong, so I prefer overwrite, what I have to do during "manual installation" phase?

View 11 Replies View Related

Debian Installation :: Segmentation Fault When Upgrading From Wheezy To Jessie

May 11, 2015

A few days ago I bought a Raspberry PI B with Debian Wheezy (7.0 - I think) on it. Before installing a media centre on it I wanted to do some basic configuration/upgrade and decided to upgrade to Debian Jessie. I followed the instructions provided on [URL] .....

Before moving to Jessie I have upgraded the original Wheezy; after the upgrade the version was 7.8. Everything went well till I executed "apt-get dist-upgrade". Errors where generated. As suggested I tried the "apt-get -f install"; but it did not go smoothly either. However, so far, I am accessing the desktop and everything seems fine (although I did not do anything fancy yet). The version recorded is 8.0. Thus, should I worry about the error messages generated?

Please find the log file here: [URL] ......

Note that I put the log file on Google Drive because each time I clicked on "add file" in the "Upload Attachment" tab when editing this message I got:

Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, forum-admin@forums.debian.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.

View 7 Replies View Related

Debian Configuration :: Wheezy - After Update Systemd Turn Off Laptop Screen On Boot

Sep 25, 2015

I decided to update all the software on my computer. Fortunately, it upgraded kernel version 3.14 to 3.16. I was happy to learn that suspend now worked on my laptop by calling pm-suspend, but it did not worked by closing the lid. So I search and found on debian's website that installing systemd and adding some config lines in /etc/systemd/logind.conf would sove the issue. So I followed the procedure and did like instructed, to end up with a computer that boots on black screen.

The last verbrose line I see on boot up is "kvm disabled by bios" and then it shutdown down the screen. The computer works, as I can login and shutdown by doing those operation blindly.

I tried removing systemd but it still does not work. If I use the old kernel 3.14 I can boot without any problem, but if I use kernel 3.16, I boot to a black screen. I remember successfully booting in 3.16 before installing systemd.

View 4 Replies View Related

Debian Installation :: Wheezy Installer Hangs Randomly

Aug 25, 2011

I'm trying to install Wheezy (amd64) from the daily netinst image with the text-based installer. The PC will lock up randomly at some point in the process (usually after about 5-10 minutes). The video signal cuts out, keyboard lights are unresponsive, and I have to hard-reset the machine.I was previously trying to install Linux Mint Debian Edition and had the same problem. Another user reports that this is due to a bug in the nouveau nVidia driver, but I can't confirm it.URL...

I assume the Debian text installer isn't using nouveau, so it seems unlikely that would be the problem. The random timing does suggest an overheating problem, though, and the fact that the video signal drops out would seem to implicate the video card. I had no lockups at all with the OS that was previously installed (Ubuntu 11.04).

View 4 Replies View Related

Debian Configuration :: Corrupted (permanent) Systemd Logs In Jessie

Apr 22, 2016

I've enabled permanent systemd logs in Jessie, and after a while I'm seeing messages about corrupted logs when checking with journalctl --verify

Code: Select allInvalid tail monotonic timestamp 0%
File corruption detected at /var/log/journal/..........

as far as I can see, there is currently no option to delete this files from within systemd facilities, is that correct?

Should they be deleted manually, or just left alone?

Apparently I can still read all older logs regardless of such reported corruption, using the journalctl --boot -n option.

EDIT:Another thing coming to mind is that this has been happening for me not only in Jessie but in every systemd-based distro that I've tried, once permanent logging is enabled: is that some kind of systemd bug?

What would exactly mean

Code: Select allFile corruption detected at /var/log/journal/38d5e6b861134eadb37cbd64b98a66bd/user-65534@d1745ac610d2459f940a24f27abd6d47-0000000000000f14-00051b8d2dabdcac.journal:000000 (of 8388608 bytes, 0%)

in particular, the 0% of 8388608 bytes part ?

View 0 Replies View Related

Debian Installation :: Upgraded To Jessie 8.2 Now Boot Hangs

Dec 4, 2015

I had Debian 7.9 up and running like a charm until yesterday. Today I did the upgrade to 8.2, now boot hangs. I see 3 boot entries for the new kernel now -

Debian GNU/Linux, with Linux 3.16.0-4-amd64
Debian GNU/Linux, with Linux 3.16.0-4-amd64 (sysvinit)
Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode)

The latter 2 entries have no problem booting up. So do the previous kernel(3.2.0.4) entries. Only the first one hangs, for which I see these 6 lines on the console:

[ 0.214704] pnp 00:04: can't evaluate _CRS: 12298
Loading, please wait...
fsck from util-linux 2.25.2
/dev/mapper/myhost-root: clean, 198627/61000000 files, 2160052/24412 blocks
[ 0.047141] kvm: disabled by bios
[ 0.000985] kvm: disabled by bios

How can I make it boot up like others?

View 6 Replies View Related

Debian Installation :: Squeeze Dist-upgrade Exited With Error Continue From?

Apr 21, 2011

I was upgrading from lenny to squeeze. At the apt-get dist-upgrade step, at some point (after upgrading and configuring) it tried to create a new certificate for my mail server but creation of the certificate failed, dpkg reported an error and the whole process exited with error. So I rebooted the machine and issued again apt-get dist-upgrade but now the certificate was created successfully . After that it upgraded mysql-client and the process finished.

But I don't know if configuring of the upgraded packages has stopped at the point where dpkg stopped. I suppose so, because very few packages were configured at that point. Is the solution to run dpkg-reconfingure -a (or -u ?) or dpkg --confingure -a or something else ? (dpkg has the PACKAGE STATES)

dpkg --configure --pending gives me no package for configuration.PS: At least I hope that all packages were upgraded and a few were not configured. Is there a way to confirm that all packages were upgraded ?

View 2 Replies View Related

Debian Installation :: Jessie RC1 Installer Hangs On Formatting Partition

Mar 21, 2015

Tried to install Jessie RC1,but installer hangs on formatting the partition,at 33%.

View 7 Replies View Related

Debian :: Spring On Wheezy But Not Jessie

May 19, 2015

I've had a weird issue recently with Java/Spring. Basically, it would work on all machines but my trusty Debian box. Macs for devs, Ubuntu for production and some devs have it too. This annoyed me, because of course Debian is the greatest and it must work there too! Also, Java is based on the whole write once run anywhere concept, I have never really had a problem with code behaving differently on different Java installs of the same version, even on completely different OSs it seems to behave itself very well. URL....

I moved up to Jessie and the problem goes away. I can only conclude that some library that is called by Java got upgraded, somehow influences the order in which Spring resolves its dependencies. Probably the fact that other devs build on Ubuntu and have got it working there, and the upgrade to Jessie brings my libs more in line with what Ubuntu will be running has done the trick.

View 0 Replies View Related

Debian Installation :: Upgrade To Wheezy Successful But No CLI And No GUI?

Jun 9, 2011

I upgraded one of my Squeeze installations to Wheezy, but after selecting it in grub, nothing is displayed on screen: no CLI and no GUI. I tried Ctrl + Alt + F[1-7] and I got nothing. My laptop is Acer Aspire 7715Z. I am attributing this to module as there seems to be disk activity, but without a screen, I cannot be certain.

View 14 Replies View Related

Debian Multimedia :: Upgraded To Jessie From Wheezy - No Sound

Jan 22, 2015

I upgraded to Jessie today and found that I have no sound.

Code: Select all# uname -a
Linux ath 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux

There is no sound card on the motherboard. Sound worked previously through HDMI from a Nvidia GTX570

Code: Select all# lspci|grep Audio
09:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1)

Code: Select all# aplay -l
aplay: device_list:268: no soundcards found...

[code]....

View 8 Replies View Related

Debian :: Upgraded From Wheezy To Jessie / Now Only GNOME Classic Works

Apr 27, 2015

I did an in-place upgrade to Jessie today and I can only get the GNOME Classic desktop, which I have to select when I log in. I had started to get used to the default desktop in Wheezy, so I'd like it back if possible. When I select gnome system default, I get my desktop, but no menus or anything I can click on at all. All I can do is ctrl-alt-delete and reboot or shutdown. I run it on a Lenovo Ideapad U410.

View 8 Replies View Related

Debian Configuration :: Udev Static Device Change From Wheezy To Jessie

Sep 9, 2015

I am using a 3rd party kernel driver that does not support udev properly. When I was using wheezy I placed the required device files in /lib/udev/devices.

The udev in jessie does not appear to support this. Is there any way to have udev create these device files or will I have to create then using a script at boot-up?

View 1 Replies View Related

Debian Multimedia :: Upgraded To Jessie From Wheezy - Sound Plays On Everything But Browsers

Dec 25, 2014

I just installed wheezy and upgraded to jessie. I had previously gotten sound working in wheezy by installing the flashplugin-nonfree and flashplugin-nonfree-extrasound packages, after configuring my headset in system settings. However, now I can't get sound to play in firefox. I've installed flashplugin-nonfree, flashplugin-nonfree-extrasound, and pulseaudio, still without luck. The volume is turned all the way up in alsamixer, sound tests play fine, and I can play music in VLC without any problems. This leads me to believe it's not a problem with drivers, but with some package I'm missing that will allow firefox to play sound. Sound wasn't working in the default video player either, before I installed the flash plugin. Is there something I'm missing?

Also, sound doesn't play on Konqueror either (KDE browser), which seems to indicate it's a problem with flash and not with firefox itself. After removing the flash plugin and installing pepperflashplugin-nonfree to ensure the pepper plugin was used instead of flash, sound still would not play in chromium, so I reinstalled the flash plugin and still don't have sound in any browser.

View 1 Replies View Related

Debian Hardware :: Android Phone No Longer Mounting Since Wheezy -> Jessie

Aug 7, 2015

Used to be, when I connected my phone and turned on USB Storage, it would automount, and I'd get a popup window asking me what I wanted to do (open and view files, or import photos with gthumb). I would just choose open and view files, move photos, music, etc. back and forth...

I would see the device listed in pcmanfm or thunar. Now, nothing happens. I do not get the popup, nor see the device in any file manager, etc. When I do fdisk -l, I do not see the phone listed, but when I do lsusb, I do see it.

Code: Select allBus 008 Device 067: ID 0482:0734 Kyocera Corp.
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It's a Kyocera Hydro Elite, an android device, set for USB Mass Storage upon connection. The phone knows when it's been connected and gives me the option to turn on the mass storage, which used to trigger the popup on the computer, but the computer no longer responds.

I have thunar-volman and mtp-tools installed.

I don't seem to have any relevant entry in /etc/fstab. Not sure if I did before upgrading to jessie from wheezy or not... I don't believe so...don't think an upgrade would wipe anything from there.

Why I'm not getting access to the phone now? Or how I can mount it without knowing it's location from fdisk? I do not use gnome, but rather plain openbox.

View 12 Replies View Related

Debian Hardware :: Lenovo ThinkPad SL410 - Upgraded Wheezy To Jessie And Lost USBs

May 8, 2015

I run Debian with Gnome on a beat up workhorse ThinkPad. I upgraded to Jessie last week with just one issue. Before the upgrade, I could plug in a USB drive (I use a couple of WD MyPassports most often) and they would mount, read, and write without a hitch.

Since the upgrade, when I plug in a USB drive, the file manager (3.14.1) sees the drive, but when I click on the drive to access/mount it, I receive a dialog box reading: Oops! Something went wrong. Unhandled error message: Error when getting information for file '/media/user/MyPassport1': Input/output error.

If I hit the little “eject” button in the file manager, then mount the drive as root from a command prompt [e.g., mount -t ntfs-3g /dev/sdb1 /media/external] I can run a directory of the drive, but ls -l /media/external fails. From the command prompt I am unable to perform reads or writes to the drive.

Rebooting into recovery mode (i.e., without Gnome), I get the same behavior with CLI messages reporting I/O errors with the drive. I can run a directory, but ls -l, reads, and writes fail.

This behavior is the same on all three USB ports. It is not limited to these MyPassport devices.

The drives work flawlessly on another headless machine upgraded to Jessie the same day. And on another still running Wheezy.

If I boot the ThinkPad from a live CD (Mint 14, I believe) the USB drives mount, read, and write fine.

My BIOS is up to date, 1.52.

lspci -v says this about USB ports:

Code: Select all00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
   Subsystem: Lenovo Device 20f0
   Flags: bus master, medium devsel, latency 0, IRQ 23
   I/O ports at 1880 [size=32]
   Capabilities: [50] PCI Advanced Features
   Kernel driver in use: uhci_hcd

[Code] .....

View 4 Replies View Related

Debian Installation :: Install Jessie From RC1 Or Do Upgrade From Stable?

Mar 7, 2015

I installed Jessie with the RC1. URL...A2) The network install images for testing (jessie) can be found at URL...However, unless you want to test the installer for testing the better choice is to use the stable installer to install a minimal stable system and then upgrade to testing by changing your /etc/apt/sources.list file.

View 8 Replies View Related

Debian Installation :: After Jessie Upgrade No WiFi / IP Address

Feb 7, 2016

I upgraded my laptop from Debian Wheezy to Jessie the other day, and just as before my wifi auto-connects to my router, and I can "ping http://www.google.com" just fine, but only for like a minute. Then the Internet access dies, but I'm still connected fine to my router, and I can ping its IP address. If I connect to the router through cable / eth0 everything works just fine, and I have full Internet access.

I assume there is something wonky with how ip address is assigned after the upgrade, how can I fix this, or trouble shoot further?

(I run Gnome desktop, with network manager).

View 10 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved