I did normal net upgrade after the official release of 10.10 yesterday evening. On reboot I get a frozen system with a blank screen. Checking via safemode, I find it is stuck when 'checking battery state' but this is a desktop machine! Apt update, uninstalling ubuntu-desktop, reinstalling ubuntu-desktop, etc.
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.
After upgrading our vmware template server from debian wheezy to debian jessie the output of the df command seems broken with regards to the root and /usr mount.We are using LVM on this machine.I've been searching for quite some time for a solution, but lack of linux knowledge is bothering me to get it fixed. The system seems to run fine without issues.
I can temporarily resolve the issue (untill next boot) by doing a lazy umount and a new mount of for example the /usr.I found a thread that something has changed in the way df presents the devices, however it is not consistent in our case (it shows a mix of both) and it seems to go wrong at an earlier stage during boot.Either show all dm devices or mapper devices is fine with me although I have a slight preference for the mapper names as it makes it more obvious LVM is being used.
I just noticed after installing a new server with samba that a portscan will show the samba used ports. This server has two interfaces, a world address eth0 and an intranet eth1. The samba ports show in scanning either interface, even after I changed samba to listen only to the intranet (192.168.x) address.
I am concerned especially about the 139 and 445 ports, which could attract a lot of garbage traffic.This is Debian 5.05 default samba installation.Otherwise similarly installed Ubuntu box with two interfaces does not show samba at all, even though smbd is running and working just fine.
I have 2x 1.5TB hard disks and I'm going to buy a new 2TB drive soon. First though I just wanted to check that I could partition off the first 1/4 to 1/3 of the 2TB drive (leaving 1.5TB or more free) and install Debian to that part, then use the remainder of the disk in combination with the 2x 1.5 TB drives in RAID 5? i.e. can you mix whole drives and with partitions from other drives in RAID 5 and/or is it best to just stick with complete drives for the RAID array?I only have room for 3 drives in the small mATX case that houses my NAS device and I want to maximise storage capacity and minimise expense.
I rebooted my vServer (Debian 8) and it doesn't came back up. Well, I used the rescue console on my server and the server seems to be running fine, except the network was broken. So I tried 'ifconfig' but nothing came up. So I tried to enable my interface with 'ifconfig venet0 up', and now it appears in my ifconfig list
My HWaddr doesn't look that well :) 'ip addr' prints this result:
Code: Select allroot@i67svof:/var/www# ip addr 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
These are the last lines in /var/log/syslog:
Code: Select allroot@i67svof:/var/www# tail /var/log/syslog Feb 20 11:34:16 i67svof systemd: Stopping memcached daemon... Feb 20 11:34:16 i67svof systemd: Stopping Network Name Resolution... Feb 20 11:34:16 i67svof systemd: Stopping Regular background program processing daemon... Feb 20 11:34:16 i67svof systemd: Stopping Login Prompts.
And finally my network config in /etc/network/interfaces
Code: Select all# Auto generated lo interface auto lo iface lo inet loopback # Auto generated venet0 interface auto venet0
I have installed Firestarter, and set it up following some manual (just a simple, baseline setting, nothing fancy). However, after restart I got error message: Starting the Firestarter firewall... failed! and then, later: startpar: service(s) returned failure: firestarter ... failed! Why this happens?
Is there a way where I can take like 50GB from my home folder (I have 375 avail., but using only 22GB) and put it to the root partition? Twice now my system has almost ran out of space on root, so luckly I was able to clear out old stuff so I don't have login issues after finding the hardway the first round lol. I just want to make sure I can login with out being forced back out because root don't have space to let me login.
I have two partitions in LVM. They are added in /etc/fstab to mount automatically. But, they are not working. The process to mount partitions seems to be happening before the service /etc/init.d/lvm2 is started. I can get it mounted using "mount -a" command, but not during the boot time. What should I do get it automatically mounted on every boot?
I have Debian Testing. I am testing XFCE and LXDE and i want to use display manager other than GDM. I have tried SLIM and XDM but when i use them i can't mount partitions and USB through Thunar, PcMan or Nautilus - i get message that i am not authorized (if i do groups in terminal - adm dialout fax cdrom floppy tape audio dip video plugdev games fuse powerdev netdev lpadmin scanner sambashare). When i install GDM everything works fine. I have installed FUSE, HAL, Udev,...I have tried a lot of stuff from AcchLinux forums but nothing worked really.
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.
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
after a reboot of my Lenny system, the default gateway will lost. Then i must try "networking restart" and the gatway will be set
my interfaces looks :
# 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
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.
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 have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
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 am having slight issue with setting up file sharing. I have a windows 7 pc and hp proliant microserver running. I have a raid array which I am using as a share for storing music, pictures etc. When I reboot the debian server I can't connect to the server from the windows 7 PC (I have mapped a network drive) until I go on to the server and restart samba with /etc/init.d/samba restart - then everything works fine. I can ping the server with both ip and hostname but the network drive does not connect - this is straight after a reboot. Is the /etc/init.d/samba restart doing something differently to when the server boots? I have read several posts relating to printer sharing issues which point to samba not starting before cups so I am wondering if samba is starting before some of the relevant networking services.