jpetersen's questions

I have a machine running Ubuntu 12.04 server with transmission-daemon running to handle bitorrents. Everything works fine except the transmission-daemon creates files as the user/group, debian-transmission, and with 744 file permissions.

• I would like to be able to delete and move these file from a samba share.

• I considered changing the primary group of the user debian-transmission, but I was worried that might mess up access to other files.

• I thought it would be better to change the default permission of new files created by debian-transmission to 774, and add myself to the group debian-transmission.

  I know that this can be done with a umask, but my understanding is that this would be set in the .profile file and since debian-transmission has no home folder I wan't sure if that file existed for the user. So how to I accomplish this?

  Suggestions or alternate solutions are welcome. Thanks in advance.

I am a little confused on the proper fstab entry for a samba share in Ubuntu 12.04

• I can get the drive to mount manually by using:

  sudo mount -t cifs //192.168.2.2/raid_drive /mnt/homeserver -o username=jon,password=password
  

• So I tried putting this in fstab:

  //192.168.2.2/raid_drive /mnt/homeserver cifs username=jon,password=password,iocharset=utf8,mode=0777,dir_mode=07‌​77 0 0
  

• Which gives me this error in syslog:

  kernel: [ 2217.925354] CIFS: Unknown mount option mode
  kernel: [ 2217.936345] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
  

• This guide says to use smbfs although I believe smbfs is deprecated?

What is a common fstab configuration for a samba share in Ubuntu 12.04?

EDIT:

Using the accepted answer below I was initially getting this error message (from dmesg):

[   45.520883] CIFS VFS: Error connecting to socket. Aborting operation
[   45.520990] CIFS VFS: cifs_mount failed w/return code = -115

although it turns out this was due to network connectivity issues, and not related to improper fstab entry.

After booting Ubuntu 12.04 64 bit, I am not able to connect to Wifi, until I disconnect and reconnect. This has been happening for a while but I am finally getting tired of reconnecting after a boot, so Im trying to fix it. In my efforts to troubleshoot here is what I have so far:

• When Wifi is not working I can not ping local network addresses

• I get the same behavior logged in as a different user

• Changing IPv6 settings to "ignore" has no effect, despite IPv6 Configure Timeout (see log below).

• Here is what I get from grep Network /var/log/syslog when the Wifi is not working :

  NetworkManager[1132]: <info> (wlan0): using nl80211 for WiFi device control
  NetworkManager[1132]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
  NetworkManager[1132]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
  NetworkManager[1132]: <info> (wlan0): now managed
  NetworkManager[1132]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  NetworkManager[1132]: <info> (wlan0): bringing up device.
  NetworkManager[1132]: <info> (wlan0): preparing device.
  NetworkManager[1132]: <info> (wlan0): deactivating device (reason 'managed') [2]
  NetworkManager[1132]: <warn> /sys/devices/virtual/net/lxcbr0: couldn't determine device driver; ignoring...
  NetworkManager[1132]: <info> wpa_supplicant started
  NetworkManager[1132]:        SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lxcbr0, iface: lxcbr0)
  NetworkManager[1132]:        SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lxcbr0, iface: lxcbr0): no ifupdown configuration found.
  NetworkManager[1132]: <warn> /sys/devices/virtual/net/lxcbr0: couldn't determine device driver; ignoring...
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: starting -> ready
  NetworkManager[1132]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: ready -> inactive
  NetworkManager[1132]: <warn> Trying to remove a non-existant call id.
  NetworkManager[1132]:        SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/virbr0, iface: virbr0)
  NetworkManager[1132]:        SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/virbr0, iface: virbr0): no ifupdown configuration found.
  NetworkManager[1132]: <warn> /sys/devices/virtual/net/virbr0: couldn't determine device driver; ignoring...
  NetworkManager[1132]: <info> Auto-activating connection 'Skylab'.
  NetworkManager[1132]: <info> Activation (wlan0) starting connection 'Skylab'
  NetworkManager[1132]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
  NetworkManager[1132]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
  NetworkManager[1132]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
  NetworkManager[1132]: <info> Activation (wlan0/wireless): connection 'Skylab' has security, and secrets exist.  No new secrets needed.
  NetworkManager[1132]: <info> Config: added 'ssid' value 'Skylab'
  NetworkManager[1132]: <info> Config: added 'scan_ssid' value '1'
  NetworkManager[1132]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
  NetworkManager[1132]: <info> Config: added 'psk' value '<omitted>'
  NetworkManager[1132]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
  NetworkManager[1132]: <info> Config: set interface ap_scan to 1
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: inactive -> scanning
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: scanning -> associating
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: associating -> associated
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
  NetworkManager[1132]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
  NetworkManager[1132]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Skylab'.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
  NetworkManager[1132]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
  NetworkManager[1132]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
  NetworkManager[1132]: <info> dhclient started with pid 2157
  NetworkManager[1132]: <info> Activation (wlan0) Beginning IP6 addrconf.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
  NetworkManager[1132]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
  NetworkManager[1132]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
  NetworkManager[1132]: <info>   address 192.168.2.9
  NetworkManager[1132]: <info>   prefix 24 (255.255.255.0)
  NetworkManager[1132]: <info>   gateway 192.168.2.1
  NetworkManager[1132]: <info>   nameserver '192.168.2.1'
  NetworkManager[1132]: <info>   domain name 'Belkin'
  NetworkManager[1132]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
  NetworkManager[1132]: <info> DNS: starting dnsmasq...
  NetworkManager[1132]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
  NetworkManager[1132]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
  NetworkManager[1132]: <info> Policy set 'Skylab' (wlan0) as default for IPv4 routing and DNS.
  NetworkManager[1132]: <info> Activation (wlan0) successful, device activated.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
  NetworkManager[1132]: <info> (wlan0): IP6 addrconf timed out or failed.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
  

  The rest is only present when Wifi is not working:

  NetworkManager[1132]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
  NetworkManager[1132]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
  NetworkManager[1132]: <info> DNS: starting dnsmasq...
  NetworkManager[1132]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
  NetworkManager[1132]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
  NetworkManager[1132]: <info> Policy set 'Skylab' (wlan0) as default for IPv4 routing and DNS.
  NetworkManager[1132]: <info> Activation (wlan0) successful, device activated.
  NetworkManager[1132]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
  

• Here is the info on my wireless card from lspci -v :

  08:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
  Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
  Flags: bus master, fast devsel, latency 0, IRQ 44
  Memory at d1d00000 (64-bit, non-prefetchable) [size=8K]
  Capabilities: [c8] Power Management version 3
  Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
  Capabilities: [e0] Express Endpoint, MSI 00
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [140] Device Serial Number 74-e5-0b-ff-ff-7d-3a-38
  Kernel driver in use: iwlwifi
  Kernel modules: iwlwifi
  

Not sure where to go with this, any help is appreciated, including tips on troubleshooting. Thanks in advance.

After downloading Juju and playing around with it a little bit, my curiosity is satisfied. I decided to move on to other endeavors and uninstall Juju, although despite my best efforts a piece of Juju lives on in my syslog (on system boot):

kernel: [   16.509086] init: juju-jon-sample-file-storage main process (2163) terminated with status 1
kernel: [   16.509113] init: juju-jon-sample-file-storage main process ended, respawning
kernel: [   16.680103] init: juju-jon-sample-file-storage main process (2164) terminated with status 1
kernel: [   16.680138] init: juju-jon-sample-file-storage main process ended, respawning
kernel: [   16.873943] init: juju-jon-sample-file-storage main process (2165) terminated with status 1
kernel: [   16.873965] init: juju-jon-sample-file-storage respawning too fast, stopped

...actual number is much greater, but you get the idea, also present is the identical errors replaced with juju-jon-sample-machine-agent.

I tried

sudo apt-get remove juju
sudo apt-get purge juju
sudo apt-get autoremove

and

sudo update-rc.d juju remove
sudo update-rc.d juju-jon-sample-machine-agent remove
sudo update-rc.d juju-jon-sample-file-storage remove

Any ideas how to remove my that last piece of Juju stuck to my syslog? I am running 12.04 64 bit. Thanks in advance.

I am getting errors when running apt-get update or when installing new packages. Although this only happens when the server configured for a static IP address. Changing the configuration back to DHCP and restarting networking fixes the problem, although I want a static IP. Once it is working I can change back to my static IP address and restart networking. Although this only works until I restart the server (restarting the router is ok), and then I start getting the same errors and have to switch back to DHCP.

Any ideas on what could be causing this or tips on troubleshooting it? Thanks in advance.

• here is my static IP configuration:

  auto eth0
  iface eth0 inet static
      address 192.168.2.2
      netmask 255.255.255.0
      gateway 192.168.2.1
  

• The apt-get update errors go something like this:

  A few of these

  Ign http://us.archive.ubuntu.com precise-backports InRelease
  

  then a lot of these

  Err http://security.ubuntu.com precise-security Release.gpg   Something wicked happened resolving 'security.ubuntu.com:http' (-5 - No address associated with hostname)
  

  and a lot of these

  W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/precise-backports/universe/i18n/Translation-en  Something wicked happened resolving 'us.archive.ubuntu.com:http' (-5 - No address associated with hostname)
  

I wanted to give a shot at deploying a Wordpress blog with Juju. Although am very new to Juju and the Amazon EC2, and am having some troubles. I am able to bootstrap an environment like this:

juju bootstrap --constraints "instance-type=t1.micro

Although I have not been successful at deploying anything. Here is the output of juju -v status:

2012-06-14 21:17:13,377 DEBUG Initializing juju status runtime
2012-06-14 21:17:13,387 INFO Connecting to environment...
2012-06-14 21:17:14,241 DEBUG Connecting to environment using ec2-50-112-192-46.us-       west-2.compute.amazonaws.com...
2012-06-14 21:17:14,241 DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="ec2-50-112-192-46.us-west-2.compute.amazonaws.com" remote_port="2181" local_port="52585".
2012-06-14 21:18:33,207 DEBUG Retrying connection: Cannot connect to environment using ec2-50-112-192-46.us-west-2.compute.amazonaws.com (perhaps still initializing): could not connect before timeout after 1 retries
2012-06-14 21:18:34,039 DEBUG Connecting to environment using ec2-50-112-192-46.us-west-2.compute.amazonaws.com...
2012-06-14 21:18:34,039 DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="ec2-50-112-192-46.us-west-2.compute.amazonaws.com" remote_port="2181" local_port="41481".

It keeps retrying although it never establishes a connection. I thought maybe it just needed some time so I tried it almost an hour later, same thing. I looked online at the AWS Management Console under Instances and I can see that the instance is running, although it doesn't seem to have any associated keypairs (when I click "connect" AWS tells me this).

I am able to start instances and SSH to them using the ec2-tools by following ec2 starters guide, and running ec2-run-instances ami-20800c10 -k ${EC2_KEYPAIR} -t t1.micro. The instances I start this way have my key-pair listed under the description tab on the AWS Instances page, and I have the option of connecting to them.

So why are the instances I am starting with Juju not getting my key-pair associated with them? I set up ~/.juju/environments.yaml as described here.

Hopefully I am not overlooking something too simple, thanks in advance for any help.

I recently setup a CUPS print server (Ubuntu server 12.04) and I having trouble with performance of a HP Color LaserJet Printer CP3505n. The printer pauses for about a second between printing each page, which is annoying when there is a lot of printing to be done. This doesn't happen when the printer is installed directly to a Windows client.

In an attempt to fix this I have setup the printer a couple different ways. I decided not to do a Samba share since this wiki said IPP is preferred.

First Method

• Added to HP LaserJet to CUPS as a Discovered Network Printer, and selected HP Color LaserJet cp3505 hpijs pcl3, 3.12.2 (en) driver. I did not use a hplip URI.

Second Method (hplip URI)

• I thought adding hplip to the mix might improve the performance, so I added the printer like this:

  • Ran hp-setup -m 192.168.2.60,

  • prompted to select driver

    Selected HP Color LaserJet cp3505 hpijs pcl3, 3.12.2 (en)

  • Used hplip to generate a URI: hp-makeuri 192.168.2.60

  • Then added the printer to CUPS as a Local Printer: HP Printer (HPLIP), and entered: hp:/net/HP_Color_LaserJet_CP3505?ip=192.168.2.60.

Either method I use I am able to share the printer on the network by adding a printer as http://192.168.2.2:631/printers/HP_LASER-TERRAC.

• Does it make a difference which way the printer is added cups?

  If so, and I install the printer with the hp URI, can I still change the driver using the CUPS web interface? I have been trying out different drivers to try and improve performance, and the cups interface is the easiest way to change them.

  Thanks in advance.

I am trying to configure rsyslog (Ubuntu 12.04 Server) to log events from a router. I found this old ubuntu forum post which got me most of the way there.

So far I am able to get the events logged from the router. However since I don't them logged in /var/log/syslog I am trying to set up a working filter in /etc/rsyslog.conf to put the logged events in /var/log/linksys.log. This is where I am having trouble.

• First I tried filtering by the router ip address like this:

  :fromhost-ip, isequal, "192.168.2.1" /var/log/linksys.log
  & ~
  

  This successfully redirects the logs as I wanted, the only problem is now I am not getting any SSHD logs in auth.log. Needless to say this is not acceptable.

• Next I tried filtering by the router name which appears in every event log:

  :msg,contains, "RV042" /var/log/linksys.log
  & ~
  

  Although this neither logs or blocks anything.

So I am stumped. I have no idea why SSHD is getting filtered with the :fromhost-ip filter. SSHD is local on the machine with rsyslog (192.168.2.2). I am thoroughly frustrated by this, any suggestions are much appreciated.