[02:32] <__Yiota>  hey guys I need urgent help, my CTO rebooted both of our google cloud engine nodes, all the data appears to have dissapeared (I can only see my user + ubuntu user), I checked df -h and the result is: /dev/sda1        49G  1.1G   48G   3% /, it should normally be at ~20 gigs or so,
[02:35] <qman__> did you have persistent disks attached for your data?
[02:36] <mybalzitch> sounds like the CTO's problem
[02:39] <qman__> I'm not that familiar with google cloud engine specifically, but I assume it works like most other cloud providers and gives you ephemeral instances, and that you need to attach persistent storage to them to store your data
[02:39] <qman__> the marketing page jibes with this assumption
[02:45] <__Yiota> qman__ yes, I did have persistent disks
[02:46] <__Yiota> I can see them with ls -l /dev/disk/by-id/google-*
[02:46] <qman__> ok, so were you storing your data there, and is it still there?
[02:46] <qman__> are those disks mounted where you expect them?
[03:22] <__Yiota> I was storing data there, the data is gone
[03:22] <__Yiota> the disks are unmounted
[03:22] <__Yiota> sorry, they are mounted
[03:22] <__Yiota> but in the wrong places
=== lutostag_ is now known as lutostag
=== chmurifree is now known as chmuri
[10:08] <c0mrade> WriteLn.Console ( " Hello " ) ;
[10:10] <c0mrade> Some weird thing happened to my server running Ubuntu 16.04.2 LTS 64bit Server on an HP ProLiant G6 server. So once I've done setting it up, I've configured a static ip, restarted the server and it worked fine, next day I wake up and can't ssh into it, I connect directly and see that the IP address is some other one assigned by DHCP.
[10:11] <c0mrade> Well I flushed the interface and restarted the networking service and it's back to the static one. But why did this happen, well actually when I physically logged in I saw some error like freezed or something and related to ata3 maybe a disk problem but anyway, even if it was why would the IP change if it's already statically configured?
[10:43] <adityaduggal> Hi I am unable to run my cron job in my server, they seem to be missed every time, can anyone help me on that?
[10:45] <adityaduggal> my cron job is this ```0 13 * * 0 sudo service nginx stop && /opt/certbot-auto renew && sudo service nginx start >> /home/frappe/log/certificate.log 2>&1 # Renew lets-encrypt every week ```
[10:45] <adityaduggal> But there is no log created and hence i am assuming that the cron job did not run, how can I test it?
[10:59] <c0mrade> adityaduggal: Hey well instead of sudo service nginx start try sudo /etc/init.d/nginx start etc...
[12:05] <ahasenack> adityaduggal: check /var/log/auth, maybe your sudo isn't working, or prompting for a password
=== marlinc_ is now known as marlinc
[12:48] <mason> c0mrade: Have you looked at /etc/network/interfaces to see what's set up there for your NIC?
[12:48] <mason> c0mrade: Also, you'll want to make sure
[12:48] <mason> ...that you don't have it controlled by NetworkManager or somesuch.
=== topi`_ is now known as topi`
[13:38] <c0mrade> mason: Um, it's not graphical.
[13:40] <mason> c0mrade: I didn't suggest that it was graphical. You still want to identify what it was that decided that it liked DHCP.
[13:40] <mason> NetworkManager is usable on text-only systems via nmcli and nmtui.
[13:41] <mason> (This is the default for RHEL 7, for instance.)
=== Isla_de_Muerte is now known as NwS
[15:49] <thebwt> also: why are you using sudo ina  cron job?
[15:49] <thebwt> just have the cron run as the system, and if it's a newer server you should use systemctl
[15:51] <thebwt> `/opt/certbot-auto renew` - if the other two commands need sudo, this should too since I assume. But we don't know about where your cert files are.
[17:30] <Dave654> Hi, I have a server with hetzner with Ubuntu 14.04.4 and Linux 4.2.0-36-generic on x86_64 the kernel never seems to update, just the dev part is this normal?
[17:30] <Dave654> its quite cool as I never boot the darn thing like all my others but...
[17:30] <nacc> Dave654: 'hetzner'? Is that a vps provider?
[17:30] <Dave654> alsorts
[17:30] <Dave654> hetzner.de
[17:30] <nacc> Dave654: the 14.04.4 hwe kernel is not supported any longer
[17:31] <Dave654> or com
[17:31] <Dave654> for English
[17:31] <nacc> Dave654: so it won't be getting updates, you should fully update to 14.04.5 hwe kernel
[17:31]  * Dave654 confused
[17:31] <nacc> Dave654: schedule is at: https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[17:31] <Dave654> ty, you would think they would tell me
[17:32] <nacc> Dave654: who is "they"? also, i think the utility hwe-support-status will tell you
[17:32] <Dave654> been like it for years tho
[17:32] <Dave654> I thought it was this modern no need to boot kernel!
[17:32] <nacc> Dave654: well, 14.04.4 only came out in feb 2016 and went eol in aug 2016
[17:32] <Dave654> they are the engineers at hetzner
[17:33] <nacc> (the kernel)
[17:33] <nacc> you would still need to reboot for security fixes, etc
[17:33] <nacc> aiui, only 16.04 has the livepatch facility
[17:33] <Dave654> never no fixes tho
[17:34] <nacc> Dave654: well, even being on 4.2.0-36 is wrong, afaict, trusty-updates has 4.2.0-42
[17:34] <Dave654> nacc does it do what it says on the tin
[17:34] <nacc> Dave654: so... just all around busted it seems :)
[17:34] <Dave654> lol thanks
[17:34] <nacc> Dave654: and probably means your system is missing some security updates
[17:34] <Dave654> ouch
[17:35] <nacc> (4.2.0-42 is in the security pocket too)
[17:35] <Dave654> never a dull moment
[17:35] <nacc> Dave654: but the correct choice is to switch the 14.04.5 hwe kernel (linux-generic-lts-xenial) and then remove the old metapackages (to save space)
[17:35] <Dave654> usually when a provider offers a OS its supported
[17:36] <nacc> Dave654: well, then ask the provider, not ubuntu server :)
[17:36] <nacc> Dave654: providers can make very poor choices :)
[17:36] <Dave654> did all I got was intense engineering waffle, stopped listening after 2 mins, basically told me do not worry
[17:38] <Dave654> will ask them again in a ticket rather than a phone call
[17:38] <Dave654> thanks
[17:39] <Dave654> what php -v does 16.04 use
[17:39] <nacc> Dave654: yeah, they should review the above page -- it seems odd they would say 'not to worry', unles they are providing their own security support on top of ubuntu's
[17:39] <nacc> !info php xenial
[17:39] <ubottu> php (source: php-defaults (35ubuntu6)): server-side, HTML-embedded scripting language (default). In component main, is optional. Version 1:7.0+35ubuntu6 (xenial), package size 2 kB, installed size 11 kB
[17:39] <nacc> !info php7.0 xenial
[17:39] <ubottu> php7.0 (source: php7.0): server-side, HTML-embedded scripting language (metapackage). In component main, is optional. Version 7.0.15-0ubuntu0.16.04.4 (xenial), package size 1 kB, installed size 9 kB
[17:39] <nacc> Dave654: and i'm going to be SRU'ing 7.0.17 to 16.04 once 17.10 opens
[17:39] <Dave654> lol 7 is out, not sure is software is up to speed
[17:40] <nacc> Dave654: hrm? sorry, i used the wrong trigger at first -- we are at 7.0.15 currently (with some backports on top)
[17:40] <Dave654> got one site not liking 5.5+
[17:40] <Dave654> cannot checkout to paypal
[17:40] <Dave654> Deprecated: mysql_escape_string():
[17:41] <Dave654> thank goodness for people like centos eh
[17:41] <Dave654> eol 2025 and good
[17:42] <Dave654> btw, sad to see 12.04 go, best OS I have ever used
[17:43] <Dave654> made a fortune off it
[17:43] <Dave654> and given back to opensource
[17:43] <nacc> Dave654: deprecated is not an error, unless you set it to be one
[17:43] <Dave654> I can fix it I think
[17:44] <Dave654> need to use mysqli
=== nacc_ is now known as nacc
=== lifeless_ is now known as lifeless
[20:19] <kotMatroskin> hi
[20:20] <kotMatroskin> - Mount snap "core" (1577) ([start snap-core-1577.mount] failed with exit status 1: Job for snap-core-1577.mount failed. See "systemctl status snap-core-1577.mount" and "journalctl -xe" for details.
[20:20] <kotMatroskin> what should I do?
[20:21] <nacc> kotMatroskin: what do the commands indicate is wrong?
[20:21] <kotMatroskin> nacc, sudo snap install nextcloud
[20:21] <nacc> kotMatroskin: right, not what i asked
[20:21] <nacc> kotMatroskin: it tells you to 'see' two commands
[20:21] <nacc> kotMatroskin: what do those commands say?
[20:23] <kotMatroskin> nacc, sorry, i speak very bad english
[20:23] <nacc> kotMatroskin: it's ok, if you can, run those two commands and use a pastebin to share the output
[20:23] <nacc> !pastebin
[20:23] <ubottu> For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic.
[20:27] <kotMatroskin> nacc, it is not bin-file, this is a command -> sudo snap install nextcloud
[20:30] <dpb1> kotMatroskin: run: systemctl status snap-core-1577.mount  and  journalctl -xe
[20:31] <dpb1> kotMatroskin: use pastebin to show us results of those commands
[20:31] <kotMatroskin> pastebin
[20:31] <dpb1> !pastebin
[20:31] <ubottu> For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic.
[20:31] <dpb1> kotMatroskin: ^^
[20:32] <kotMatroskin> what is pastebin?
[20:32] <nacc> kotMatroskin: please read the response from ubottu
[20:33] <kotMatroskin> results of those commands: Failed to mount Mount unit for core.
[20:33] <kotMatroskin>  
[20:33] <nacc> kotMatroskin: there will typically be more output than that
[20:33] <nacc> kotMatroskin: please run the command don't select what put on paste.ubuntu.com
[20:34] <nacc> kotMatroskin: but copy & paste the entire output
[20:34] <nacc> kotMatroskin: or use pastebinit directly from the terminal
[20:36] <kotMatroskin> result of systemctl status snap-core-1577.mount:
[20:36] <kotMatroskin> root@vps24182:/home/alex# systemctl status snap-core-1577.mount
[20:36] <kotMatroskin> ● snap-core-1577.mount - Mount unit for core
[20:36] <kotMatroskin>    Loaded: loaded (/etc/systemd/system/snap-core-1577.mount; enabled; vendor preset: enabled)
[20:36] <kotMatroskin>    Active: failed (Result: exit-code) since Mon 2017-04-17 16:35:00 EDT; 1min 29s ago
[20:36] <kotMatroskin>     Where: /snap/core/1577
[20:36] <kotMatroskin>      What: /var/lib/snapd/snaps/core_1577.snap
[20:36] <kotMatroskin>   Process: 690 ExecMount=/bin/mount /var/lib/snapd/snaps/core_1577.snap /snap/core/1577 -t squashfs (code=exited
[20:36] <kotMatroskin> Apr 17 16:35:00 vps24182 systemd[1]: Mounting Mount unit for core...
[20:36] <kotMatroskin> Apr 17 16:35:00 vps24182 mount[690]: mount: /snap/core/1577: mount failed: Unknown error -1
[20:36] <kotMatroskin> Apr 17 16:35:00 vps24182 systemd[1]: snap-core-1577.mount: Mount process exited, code=exited status=32
[20:36] <nacc> kotMatroskin: please use a pastebin, as asked
[20:36] <kotMatroskin> Apr 17 16:35:00 vps24182 systemd[1]: Failed to mount Mount unit for core.
[20:37] <nacc> kotMatroskin: you're flooding the channel
[20:37] <kotMatroskin> Apr 17 16:35:00 vps24182 systemd[1]: snap-core-1577.mount: Unit entered failed state.
[20:37] <kotMatroskin> what is pastebin?
[20:37] <nacc> !pastebin | kotMatroskin: please read this, again, as asked
[20:37] <ubottu> kotMatroskin: please read this, again, as asked: For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic.
[20:37] <kotMatroskin> bash: pastebin: command not found
[20:37] <nacc> kotMatroskin: a pastebin is just an online service for sharing pastes
[20:37] <nacc> kotMatroskin: yes, *read* the blurb from ubottu.
[20:40] <kotMatroskin> ok, must back in the morning. thank you
[20:41] <rizonz> this is weird only my  boot chainload into bootloader on the first disk - alternative for pxe boots from disk
[20:41] <nacc> kotMatroskin: you might, in the morning, ask in #snappy -- as the core snap failing is not really a server issue