Debian Configuration :: Jessie Upgrade Ssh Command Line Reboot
Nov 13, 2015
I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
I've been using various distros of Linux for over 20 years - but I'm stumped.
Was running Mint. But after taking an update a few weeks ago the network stopped working. After a lot of time and effort decided to give up on Mint and switch distros to Debian 8 Jessie.
But after changing the Network settings from default DHCP to my usual IPV4 static 10.net configuration and rebooting the network will not work.
I have several systems on a 10.100.0.0/16 LAN behind another Linux system acting as firewall/gateway.
Now, after about 7 hours of mining the Internet, I still can't get basic networking to work:
- Have tried a few combinations, with and without Network Manager and eth0 in interfaces - /etc/network/interfaces is configured with a static IP and relevant parameters - ifconfig shows eth0 and the correct information - netstat -rn shows the basic default route to the gateway - have tried with IPV6 enabled and disabled; it is not used on my LAN
The box is a desktop system, ASUS Maximum VI Formula mobo with onboard Ethernet, dual GTX 780 cards. Nothing very weird.
It all LOOKS right, but ping can't get off the box "destination unreachable", and no other system on the LAN can ping it.
I'm amazed a basic static IPV4 network setup completely breaks it. This is my main workstation - a dual-boot system where Windows runs fine - so it's not hardware.
EDIT: This has been solved. See the solution post: [URL]
I set the file as executable. sudo chmod +x /etc/init.d/myshutdown.sh
I inserted a symlink in the rc0.d directory with the process order K04. sudo ln -s /etc/init.d/myshutdown.sh /etc/rc0.d/K04myshutdown.sh
I also inserted a symlink in the rc6.d directory with the process order K04. sudo ln -s /etc/init.d/myshutdown.sh /etc/rc6.d/K04myshutdown.sh
Apparently rc0.d is for shutdown and rc6.d if for reboot
After reboot it appears that rtorrent does not run (I cannot connect to rtorrent via rutorrent) but really what is going on. I am trying to do this because rtorrent does a hash check on all files if it is not shutdown properly. I just want it to shutdown automatically and safely, before the system shuts down.
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
I installed the Open Source Media Center (OSMC) on my Raspberry Pi 2. It's based on Debian Jessie. I bought a Blueooth Keyboard (Keysonic KSK-3211) and an USB-Bluetooth adapter (CSL Bluetooth Stick Nano). And now I am looking for a way to pair the keyboard with the raspberry via command line.
I'm new to all this bluetooth stuff in debian. It's the first time I try to install it. As far as I've understood I need an agent that is started with the pairing PIN. Then I type this PIN at the keyboard and that's it. Am I right?
The problem is, that every agent I've found in howtos or descriptions like bluez-simple-agent or bluetooth-agent (like described here [URL] ....) is not installed (and as far as I know can't be installed) under Jessie.
The bluetooth adapter is recognized
Code: Select allosmc@osmc:~$ hcitool dev Devices: hci0 00:1A:7D:DA:71:0C the keyboard is found Code: Select allosmc@osmc:~$ hcitool scan Scanning ... 00:12:A1:70:42:28 Bluetooth Keyboard
And I can ping the keyboard
Code: Select allosmc@osmc:~$ sudo l2ping 00:12:A1:70:42:28 Ping: 00:12:A1:70:42:28 from 00:1A:7D:DA:71:0C (data size 44) ... 0 bytes from 00:12:A1:70:42:28 id 0 time 14.82ms 0 bytes from 00:12:A1:70:42:28 id 1 time 9.91ms 0 bytes from 00:12:A1:70:42:28 id 2 time 32.62ms 0 bytes from 00:12:A1:70:42:28 id 3 time 28.81ms ^C4 sent, 4 received, 0% loss
So everything seems to be ok ... but I can't find the command for pairing the keyboard. Looks like something changed in Jessie so that the old tutorials are outdated.
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.
I had a Linux server with Wheezy, I have 2 internal drive, one for linux OS, the other our Video On Demand drive that must be accessible to Windows and online. (That's why I chose NTFS, with our large video files, FAT will not work, and EXT isn't compatible with windows sharing, and I haven't gotten FTP to work right .
So I upgraded to Jessie today, and everything went smoothly until I tried to access my NTFS drive. (Named WowzaStorage)
I used FSTAB to auto-mount the drive (/dev/sdb1) to /media/ntfs/ on boot. All of this worked swimmingly on Wheezy, but since the update, something got mucked up and I cannot figure it out.
When accessing the mounted NTFS folder in /media/ (if it even shows up) gives me a 'Cannot be found' 'Input/Output error'
When in gParted to examine the drive, I can select it and view all the correct info, but I keep getting "error informing the kernel about modifications to partition /dev/sdb1/ --invalid argument"
Now first I thought maybe the NTFS driver was faulty and I removed 'ntfs-3g' and reinstalled it.
Now when I am in Terminal, after i umount and mount sdb1, I can CD to the drive but not the folders on it... Also using the File Browser, I get errors, and missing folders.
I get "Unhandled error message: Error when getting information for file '/media/ntfs': Input/output error"
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
I find the next one. When I boot into jessie my RAID device (just a data partition not /) is not found causing the boot to fail as per problems reported here
After booting I can mount my RAID device but if it's in the fstab when booting it fails. Also, I notice that some of my lvm device names have changed. After a bit of hunting around I found a couple of solutions pointing to running dmraid as a service during boot and changing the entry for the RAID device in fstab to use the UUID.
This seems to work. However this seems to be a workaround and as the lvm device paths for my / and /usr partitions have also changed, I'm wondering if there is a bug here as mentioned in the second link?
The / and /usr paths changed to /dev/dm-2 and /dev/dm-3 from the /dev/mapper/ form.
I had a pretty much standard installation according to some tutorial (I don't remember, which one) for courier, including ssl. After upgrading from Wheezy (7) to Jessie (8) everything continued working fine, excep ssl connections to pop or imap.
In the log I get this error message while connecting to imapd-ssl:
--- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 341 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE ---
TLS over STARTTLS is also not working and does not invoke a log-entry. So I want to solve the ssl-problem first. I guess the STARTTLS-problem is automatically solved then.
My update procedure was:
Editing /etc/apt/sources.listapt-get updateapt-get upgradeapt-get dist-upgradeKeep all configuration files regarding courier.
I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.
STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid [2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 3704): assert failed: pjob->jobid == jobid [2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames:
last week while I was using ssh to the computer1 inside a NAT as usual, I made another tunnel from the computer1 that I was connecting to, to another computer2 inside that NAT (ssh 192.168.1.130) and after making some changes in computer2 I typed reboot. The computer2 rebooted but the tunnel totally hung and I had to kill it in my laptop. Since that day I haven't been able to ssh to the computer1 as I am used to.
Here is some more information:
debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/une/.ssh/id_rsa
I wanted to be able to have a boot option to just use a command line with no X running at all. What I did was remove the gdm3 link in rc5.d . Then in /boot/grub/grug.cfg I made a new menuentry that is exactly the same as the default but I changed this line:
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=3e926e70-cb92-4847-997c-37aabda532ff ro quiet to this line: linux /boot/vmlinuz-2.6.32-5-686 root=UUID=3e926e70-cb92-4847-997c-37aabda532ff ro 5
This worked. It gave me a command line interface with no X running.
My question is is this the recommended way in Debian? If not what is?
I have been using Linux for a very long time but I used mostly Slackware. I tried Redhat for awhile but really hated bluecruve, shows how long I have been using Linux. I have played with other distros but I always went back to Slack. But I really dislike KDE4 so Slack is no longer an option. KDE4 reminds me of a 12 year old girl that got a big box of makeup and had to use every bit of it. I now am using Debian on my laptop. And as aside I gave my 16 year old daughter a laptop for her birthday. She used the included version of windows 7 for awhile but then asked me what would be a good Linux distro for her. I showed her distrowatch and told her to look at the top distros. She then asked me to help her put on Debian. She loves it. She is a very good musician and song righter, She actually gets paid for doing that at 16, and really likes the programs in Linux to work with sound files. She also does MIDI stuff with our Yamaha Clavinova.
Now we are trying to do things the Debian way and it is a little different then other distros. So did I do the command line thing they way it's recommended in Debian. I have looked on line but all I could find was working in a shell and that is not what I was looking for.
I use Huawei EC1260 modem for mobile broadband connection. What are the command line shell based ppp dialing applications available apart from wvdial? insight how to use pppd/chat directly.Actually wvdial is working on debian very well with this modem. But I need to use it on an arm le based system, where wvdial does not work properly because of setcontext(), getcontext() dependency on arm platforms.
I'm running a desktop-less version of Debian via Sun VirtualBox. The reason I'm doing this is because I don't have enough graphics or RAM power to have a desktop environment running on top of my current desktop; also, I want to learn Linux through the command prompt. I'm running the AMD64 version of Debian; I'm not sure if that's relevant.
My main goal is to be able to email useful files from the virtual Debian to my main computer, so that I can save them for later if I ever decide to do a "real" installation of Debian on this computer. I realize now that there's probably some "easy" way to do this by reading the virtual machine's hard drive, but at this point, my curiosity wants to see this issue resolved. I started off wanting to find a command-line program to send my email with, and one was built-in. The syntax ~$ sudo mail -s "Subject" email@example.com "This is a test email."
C^D Cc:C^D ~$
is what I found. I tried it, and (unsurprisingly), it failed. I then learned that the mail command calls exim4, or something along those lines, so I needed to configure exim4. Soon thereafter, I learned that Yahoo's SMTP wasn't public, but Google's was. So, I found this web page which described how to configure exim4 to allow for email to be sent to a Gmail account. I made one, and followed the page word-for-word.
I sudo-mailled a test email to my Gmail account, and nothing happened. I waited a bit longer, and still, nothing happened. Finally, I started looking around, and found out about the exim4 logs in /var/log/exim4. In my mainlog, I think that it's telling me that Google denied my connection: <date><time><random numbers and letters> == **********.gmail.com R=send_via_gmail t=gmail_smtp defer (111): Connection refused
So, now, I'm just stuck. I don't know what I did wrong, I checked my exim4.conf.template twice for spelling errors, but I don't think I made any. At this point, I can only hope that someone else has had a similar problem, or knows what I'm doing wrong (or haven't done yet).
since I am on a Dell inspiron 1545 laptop, being able to display my battery charge is critical. After some extensive googling, I found I need a command 'acpi', which does not exist on my computer. I cannot seem to find it in the packages database; the closest thing being 'acpi-support' apt-get install also can't find it.
I tried cat /proc/acpi/battery/BAT0/state, but that only shows me if the battery is discharging or charging and doesn't give me an actual percentage.
I would like to know if I can reboot my headless ubuntu machine from command line to a different OS on the same disk. To clarify, I want to do this without having to manually choose in GRUB.
OS1: Ubuntu on sda1- it is the default OS in an always on server.
OS2: Fedora on sda2 - have to login into this once in a while.
There are no monitors attached with the machine. So I cannot manually scroll through grub and choose Fedora. I want to know if there is a command I can issue remotely to the Ubuntu server to reboot to Fedora.
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
It seems like ifconfig used to show which DNS servers were being addressed, but something has changed, I need to know whether I am referencing what I think I am... I have search this forum, googled, and come up empty... did the metrics go away with 8.2? Was I dreaming at 7.5?
I have a relative fresh install of jessie in which I face a high cpu usage of java (top shows about 165% CPU and 12% MEM). The problem occurs right after booting the computer. These values stay constantly high for days if I leave the box running. This happens even if the computer is just sitting there without doing anything.
I have to kill java to go back to normal. So, when I do a Code: Select allkillall -KILL java the problem goes away. After that it doesn't reappear and I can use all apps installed without a problem.
Currently I am based on openjdk Code: Select allupdate-alternatives --display java java - auto mode link currently points to /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java - priority 1071 slave java.1.gz: /usr/lib/jvm/java-7-openjdk-amd64/jre/man/man1/java.1.gz Current 'best' version is '/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java'.
But I have also tried the SUN version with the same result.
Where to look to find more information on what exactly java app is using so much resources and how I can solve it? I guess I could just put somewhere in rc.d a kill java command and forget about it but I would really like to find out whats going on...
When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.
I am having trouble using touch pad in jessie. My touch pad was ok when it's in wheezy but after i updated to jessie, i can't really get used to it.
I don't know whether i setting it up wrongly, sometimes, my touchpad will keep dragging, without releasing. And if I click the bottom right of the touch pad, it's not right click; instead i have to use two fingers.
etc. So how can i change to back to a more traditional usage? Also, do jessie have a setting like ubuntu saying disable touch pad while typing?
After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
A few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.
umount My passport fdisk -l (to see device name) mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4 dmesg | tail [ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found [ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through