[01:47] <IlliteratePhilos> hey anybody up for helping a noob learn how to set up a server to host a website I want to make from home?
[01:47] <IlliteratePhilos> I really don't know where to start
[06:29] <FilthyMacNasty> hilo ubuntu peeples
[07:25] <lordievader> Good morning.
[07:29] <FilthyMacNasty> guten tag lordievader
[07:30] <lordievader> Hey FilthyMacNasty, how are you?
[07:30] <FilthyMacNasty> having a bad computer day
[07:30] <lordievader> Do such things exist?
[07:31] <FilthyMacNasty> yes, I had the sewer manager touch today
[07:32] <FilthyMacNasty> turns out my partner downloaded our image of 12.04 server from a torrent, the entire sources list said trukty not trusty
[07:33] <lordievader> Hehe, that's fun ;)
[07:33] <FilthyMacNasty> 4 installs and 4 epic failures
[07:34] <FilthyMacNasty> so now I'm at the brainbleach
[07:35] <lordievader> FilthyMacNasty: Download an image from Ubuntu itself.
[07:35] <sarnold_> .. or at least check the signatures :)
[07:36] <FilthyMacNasty> like I said, my partner did it while I was onsite
[07:37] <FilthyMacNasty> he's in a roll of carpet with some quicklime in a hole outside town
[07:37] <lordievader> Was it a reinstall or a new deployment?
[07:37] <sarnold_> poor carpet
[07:37] <FilthyMacNasty> fortunately 2 were experimental 1 was a laptop for a  user and 1 windows box was being contrary
[07:39] <FilthyMacNasty> the windows box has slic 2.1 in the bios, but its hidden by dell and will not authenticate
[07:40] <FilthyMacNasty> so I been playing the "remember hex" dance all day
[07:41] <FilthyMacNasty> turns out its windows 7 pro slic
[08:29] <Yossarianuk> hi - just seen 14.04 has another libssl update -> 1.0.1f-1ubuntu2.7 is this just related to the poodle attack or are there other issues fixed also ?
[08:30] <maxb> Perhaps you should read the package changelog?
[08:30] <sarnold_> Yossarianuk: it also has several DoS fixes: http://www.ubuntu.com/usn/usn-2385-1/
[08:35] <Yossarianuk> sarnold_: thanks
[09:27] <_ruben> what is the "recommended" HA cluster suite these days? all pacemaker/corosync stuff seems to end with howtos for 12.04
[09:45] <jamespage> _ruben, pacemaker/corosync is still good
[09:45] <jamespage> rbasak, re https://bugs.launchpad.net/ubuntu/+source/websocket-client/+bug/1374335
[09:45] <jamespage> are you going to chase that?
[10:07] <_ruben> jamespage: most howtos mention the cman package, but that's no longer present in trusty. not sure how critical that is tho
[11:04] <roaksoax> /w/win 17
[11:31] <dine909> does /etc/network/interfaces.d/ work yet?
[11:32] <dine909> when i put an interface definition in there it doesnt seem to get picked up
[11:32] <sarnold_> dine909: I think you need the source-directory interfaces.d line from interfaces(5)
[11:39] <ochoroch> lordievader: Hey ... u remember the issue i have? ... it was that misterious SHH login problem ...
[11:40] <ochoroch> lordievader: as mentioned last time i have 3 Servers running on ubuntu 14.04. Only one had this issue. I just installed TYPO3 (cms, php and mysql) on one of the "as working" considered servers and guess what?
[11:41] <ochoroch> next morning that server had the same behavior: No ssh login possible ...
[11:42] <ochoroch> and the same messages in console ...
[11:44] <sarnold_> o_O
[11:44] <sarnold_> what messages i nthe console?
[11:45] <ochoroch> one sec ...
[11:45] <dine9091> thanks sarnold_ did the trick
[11:47] <ochoroch> sarnold_: http://picpaste.com/Bildschirmfoto_2014-10-15_um_08.26.21-QunlBobe.1413359450-tQYnSQ0b.png
[11:50] <ochoroch> sarnold_: all 3 are virtual Maschines running on HyperV ....
[11:50] <sarnold_> dine9091: nice
[11:50] <XpineX> Hi, I have used targetcli on my server to create an iSCSI target. How do I see the clients that are logged in to that target?
[11:51] <sarnold_> ochoroch: interesting. might be worth using sysctl to snyc, umout, reboot, and check the logs for the start of the issue..
[11:55] <ochoroch> sarnold_: a little more verbose please ... :-)
[11:56] <sarnold_> ochoroch: you can use the magic sysrq key to sync disks (sysrq+s), umount filesystems (sysrq+u), and reboot (sysrq+b), it's not a clean shutdown but shouldn't be too horrible
[11:56] <sarnold_> ochoroch: then you can check in /var/log/syslog for hopefully some kind of warning about what locked up
[11:57] <ochoroch> ok ....
[11:58] <cwillu_at_work> magic-sysrq is disabled on new enough ubuntu
[11:58] <cwillu_at_work> which is annoying
[11:58] <sarnold_> argh
[11:58] <sarnold_> I forgot :/
[11:58] <ochoroch> ok ...
[11:59] <cwillu_at_work> not sure who to blame for that
[11:59] <dasjoe> It's disabled? I thouhgt it was masked to 176
[11:59] <dasjoe> What does "cat /proc/sys/kernel/sysrq" return?
[12:01] <cwillu_at_work> disabled enough to be disruptive to me on a daily basis
[12:01] <sarnold_> dasjoe: that's the thing, he can't log in
[12:02] <cwillu_at_work> looks like syn, umount and reboot should work though
[12:02] <dasjoe> cwillu_at_work: sub should still work
[12:02] <cwillu_at_work> yeah, but that's not the only use of sysrq :p
[12:03] <cwillu_at_work> all sorts of fun telling people "hit alt-sysrq-t and pastebin your dmesg" when trying to troubleshoot deadlocks, only to find that sysrq-t doesn't do anything anymore :p
[12:03] <dasjoe> Though probably the most important one ;)
[12:03] <cwillu_at_work> depends on who you're talking to
[12:04] <cwillu_at_work> and I still think the security benefits are questionable
[12:04] <cwillu_at_work> physical access outside a kiosk still lets you do the same things
[12:04] <cwillu_at_work> and kiosks already require many more manual adjustments
[12:16] <tafa2> Can anyone recommend a good SSH app for Mac to organise multiple SSH connections - something a bit more structured than iterm or standard terminal?
[13:11] <lordievader> ochoroch: Err, please jog my memory...
[13:18] <ochoroch> lordievader: sorry for the delay ... you want the full story?
[13:18] <lordievader> ochoroch: Sure, why not ;)
[13:18] <ochoroch> i have 3 Ubuntu VMs running on HyperV gen1. ....
[13:19] <ochoroch> Ubuntu Version is 14.04. It just worked. ...
[13:20] <ochoroch> i had trouble with the disk failing/read-only every now and then ...
[13:21] <ochoroch> i was able to fix this by installing all the required drivers and such ... doing a full fsck in recovery mode seems to fix this.
[13:21] <ochoroch> .. ok... after this i thought "yeah man, i made it" ....
[13:23] <ochoroch> but the day after i got this when i tried to login: http://picpaste.com/Bildschirmfoto_2014-10-15_um_08.26.21-QunlBobe.1413359450-tQYnSQ0b.png
[13:23] <ochoroch> thisw is the current ecisting issue, it occurs after roughly 16 hours .....
[13:23] <ochoroch> i cant login anymore ...
[13:24] <ochoroch> ssh promts for password, but does not do a thing.
[13:24] <lordievader> Ah, right. That screenshot reminds me.
[13:24] <ochoroch> when ic force it to turn on/off again it works ....
[13:25] <lordievader> ochoroch: Is your machine swapping heavily at that time?
[13:26] <ochoroch> no ... its bored ...
[13:26] <lordievader> ochoroch: Appearantly those type of messages are given when it does not respond.
[13:26] <ochoroch> no swap at all ...
[13:26] <lordievader> Heavy io wait?
[13:26] <ochoroch> in addition: coz of the fact the other 2 machines seemed to work well for 2 weeks now i decided to put a website (TYPO3 CMS: php and mysql driven) on one, the same happend the this maschine ...
[13:27] <ochoroch> lordievader: io wait, i'll check my stats ...
[13:27] <sarnold_> hmmmm, I remember seeing some bug with vmware not writing zeros properly...
[13:28] <ochoroch> lordievader: io wait seems normal ...
[13:28] <sarnold_> a -little- iowait is normal, 120 seconds is lunacy :)
[13:28] <sarnold_> here's the bug I was thinking of, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591
[13:29] <ochoroch> sarnold_: ok ...
[13:30] <sarnold_> ochoroch: just skim it, see if it looks familiar to you..
[13:30] <ochoroch> sarnold_: yep ...
[13:33] <ochoroch> sarnold_: ok ... i "think" i need to install https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591
[13:34] <ochoroch> sorry install these guys; http://people.canonical.com/~arges/lp1371591/
[13:34] <ochoroch> i'll give it a go ....
[13:35] <sarnold_> ochoroch: good luck :)
[13:35] <ochoroch> just made a "snapshot" ....
[13:35] <ochoroch> :-P
[13:36] <ochoroch> but thanks! ...
[13:49] <rbasak> jamespage: re: bug 1374335, not currently. Sorry, I should have made it clear that from the juju-quickstart end, they aren't chasing the release team and are OK with it slipping to V.
[14:02] <NelsonMinar> how do I debug a problem with udev and my ethernet device being named /dev/p4p1 instead of /dev/eth0? /etc/udev/rules.d/70-persistent-net.rules is being ignored, maybe because I installed udevname?
[14:02] <NelsonMinar> it's a remote server without console access, so getting this wrong is.. awkward. already had to call in the remote admin once.
[14:03] <patdk-wk> heh? it's not something you debug
[14:03] <patdk-wk> that is *working* as designed :)
[14:03] <NelsonMinar> I'm confused as to why it's named /dev/p4p1 when the file in /etc/udev/rules.d says to name it eth0. I think the presence of biosdevname may be causing that, but I'm not sure and am confused by the docs.
[14:05] <patdk-wk> well, uninstall it
[14:05] <patdk-wk> update your initramfs
[14:05] <patdk-wk> and reboot
[14:06] <NelsonMinar> patdk-wk; I'm not in a position to do experiments (no console access). is how biosdevname interacts with device naming documented somewhere you know of?
[14:06] <patdk-wk> in the manual :)
[14:06] <patdk-wk> http://manpages.ubuntu.com/manpages/saucy/man1/biosdevname.1.html
[14:07] <patdk-wk> but it's used on startup
[14:07] <NelsonMinar> yes thank you, I've read that a few times. It does not describe how ubuntu's boot process uses it. If you don't know the details on how this stuff works, that's OK, was hoping someone here did.
[14:08] <patdk-wk> uninstall it, update initramfs (or it will still exist)
[14:08] <patdk-wk> and reboot, then it's gone, and not renaming
[14:08] <patdk-wk> the issue is, udev works
[14:08] <patdk-wk> device made, eth0, udev sets it to what it should
[14:08] <patdk-wk> then biosdevname changes it again
[14:10] <NelsonMinar> is the way biosdevname interacts with udev documented somewhere? it's not the man page you linked.
[14:10] <patdk-wk> I don't know that it even interacts
[14:11] <Pici> Theres a mention of a udev rule in the biosdevname package description.
[14:11] <patdk-wk> hmm, don't have biosdevname installed anywhere
[14:11] <NelsonMinar> Pici: thanks! that's helpful. it installs /lib/udev/rules.d/71-biosdevname.rules
[14:12] <patdk-wk> so it's 71
[14:12] <patdk-wk> so change it to be a lower number?
[14:12] <patdk-wk> since the persistant net naming is 70
[14:14] <ochoroch> lordievader: sarnold_: installed kernels and friends as suggested in the ticket. straight away notices ssh login is faster and smoother ....
[14:14] <ochoroch> i gotta wait till monday and report back! ....
[14:15] <ochoroch> lordievader: sarnold_: thanks ! ... really appreciate your help....
[14:19] <NelsonMinar> heh, here's a bug saying the Ubuntu Server guide has not been updated for 14.04, with how ethernet device naming works. https://bugs.launchpad.net/serverguide/+bug/1312785
[14:26] <NelsonMinar> read more; I think installing biosdevname caused my device to be renamed in udev and now the old /etc/udev/rules.d/70-persistent-net.rules is being ignored. gonna do some more tinkering and then reboot, will update that Ubuntu bug for the record. I think new 14.04 installs may work differently from do-release-upgrade systems.
[14:56] <MasterRoot24> I have `CustomLog ${APACHE_LOG_DIR}/example.com_access.log combined` in an Apache vhost config, however I am only getting the string "combined" logged to the log file on each request. Anyone have any ideas why this would happen?
[14:58] <NelsonMinar> is "combined" defined as a log format? Relevant docs: http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#customlog
[14:58] <rbasak> MasterRoot24: have you defined what "combined" means in a LogFormat directive?
[14:58] <rbasak> Yeah, what NelsonMinar said :)
[15:00] <MasterRoot24> rbasak: Possibly not, I'll check!
[15:08] <MasterRoot24> NelsonMinar: rbasak: Thanks guys - turns out someone had commented out the respective LogFormat lines. Uncommenting those lines fixed the problem.
[15:08] <NelsonMinar> \o/ hooray
[15:35] <NelsonMinar> last comment about my udev drama: system rebooted fine. I removed the 70-persistent-net.rules that was being ignored. it appears simply installing biosdevname is enough to cause devices to be renamed next time you boot.
[15:39] <patdk-wk> that was a given :)
[15:40] <NelsonMinar> and yet it's not documented anywhere. I updated the bug.
[17:01] <Guest83311> ciao non vedo un disco SCSI su un server. Ho lanciato il comando parted -l e mi ha restituito questo -> http://paste.ubuntu.com/8580059/
[17:02] <lordievader> !it | Guest83311
[18:20] <phillw> Hi, any ubuntu-server admins about? F.Y.I. bug 1380774 has a fix, but note 20141017 Ubuntu Server does NOT have the right version of apt. A release manager needs to check that apt is version 1.09-2ubuntu2 and then ask for a respin.
[21:01]  * donspaulding prepares to quote himself from the main #ubuntu channel
[21:01] <donspaulding> Hi there, I'm using n2n to setup multiple VPN interfaces on a single host.  I would like to use avahi/mDNS to broadcast a different hostname tied to a different IP address on each device.
[21:01] <donspaulding> For example, if I have a 'prodvpn0' interface and a 'testvpn0' interface, each with their own IP (assigned by avahi-autoipd), how can I have avahi-daemon broadcast the mDNS hostname as mybox.testvpn.local on the testvpn0 interface and mybox.prodvpn.local on the prodvpn0 interface?
[21:01] <donspaulding> I tried creating individual upstart scripts pointing to different avahi-daemon.conf files, but avahi-daemon refuses to start when it detects a running daemon.
[21:25] <semiosis> donspaulding: are you using an 'instance' stanza in your upstart jobs?  http://upstart.ubuntu.com/cookbook/#instance
[21:26] <semiosis> donspaulding: one upstart job, using an env var for the config file & the instance line
[21:26] <semiosis> might do the trick
[21:26] <semiosis> if it's just an upstart issue
[21:26] <semiosis> sounds like it's not though
[21:30] <donspaulding> semiosis: I hadn't seen instance before, thanks for pointing that out.
[21:31] <donspaulding> semiosis: but your guess is correct, it's not an upstart thing.  In this case, the avahi-daemon process is looking around for other running processes after upstart spawns it, but before it begins functioning.  If it finds another avahi-daemon process, it bails out.