[04:27] I am not able to update "sudo apt update|more [04:27] WARNING: apt does not have a stable CLI interface. Use with caution in scripts. [04:27] Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease [04:27] Cannot initiate the connection to archive.ubuntu.com:80 (2001:67c:1560:8001::11). - co [04:27] nnect (101: Network is unreachable)" [06:11] good morning [07:20] Good morning === lotuspsychje_ is now known as lotuspsychje [13:53] jamespage: sahid: I'm working through promotions to -updates across the cloud archives for anything that's verified [13:55] coreycb: ack, can i help on anything? [13:56] sahid: I think at the moment we're ok, thanks. got a lot of things verified last week and just need to get them released. [13:57] ack, i'm trying to fix packages that are failling autopkgtest so [14:11] coreycb: awesome thanks [14:14] sahid: thanks, good idea. if you come across networkx, I have that covered. I'm working on fixing up the component mismatches for that but also hitting other issues with it. [15:53] coreycb: Are you aware of these deprecation warnings for train cinder on 18.04? https://paste.ubuntu.com/p/Svw5CsZpsM/ [15:55] coreycb: I guess they are more of OpenStack's problem and not Ubuntu. The one about policy enforcement is annoying though because I don't even use a cinder policy file and just rely on the built in "sane defaults".. which maybe are deprecated and causing this warning too? [15:55] shubjero: hi, I don't think I've seen those. yes that would be my next question is whether they are an upstream issue or limited to our package code. [15:55] shubjero: we try to use upstream config by default as much as possible whether that be the static copy from usptream source or a generated copy based on how upstream generates (ie. tox.ini) [15:56] shubjero: right and policy is in code mostly now [15:57] coreycb: Yeah, it looks like I probably have to ignore these warnings for now and drop them from my ELK stack as its fairly frequent and clutters the logs [16:00] shubjero: it'd be worth getting a bug opened upstream if it looks it's not yet fixed in master and there isn't already a bug open. unless your deployment tooling is possibly laying down any policy config. [16:03] coreycb: yeah ill look at upstream [16:03] coreycb: thanks [18:19] how could i make sure i actually write to a disk mounted at mount point rather than the mount point itself in root disk or how does it work? I could do a conditional in my script and grep output of mount command is there another way though?? [18:24] vlm, what does this script do, and how will it be run? [18:25] vlm, an easier way might be to touch a flag file inside the mount, and check for its existence. Alternatively, if this will be run as a systemd service, you can have systemd check [18:27] lordcirth: ohh you mean like create a lock file of some sort?That ive done before didnt remember ,thats actually good enough for thanks! [18:27] vlm, you could lock it as well, but simply "if this file is here, then it's mounted, because this is only on the mount" works [18:28] lordcirth: ive done that before thats just whats needed then i just exit script if its not present [18:31] vlm: you might want to use "mountpoint" to test if the dir is a mountpoint or not [18:32] sdeziel: thats another good suggestion aswell thanks,always these usefull commands laying around always forget about or dont discover [21:03] Q: if I clone a partition with hard links, am I going to have any issues on the new drive? [21:03] I've been trying to rsync -avrH the contents and I'm 4 days into a 1.4TB copy, its killing me [21:23] i i forward all syslog to services is all logs of my system will be captured ? [21:23] is there any thing else to capture ? [21:25] fluvvel: you should have no issue with the new drive but yeah, rsync can take a while (newer rsync versions (3+) are better) [21:26] fluvvel: are you rsync'ing a BackupPC pool or a rsnapshot partition? [22:28] sweb: some things may be logged only to the systemd journal; other applications will log to their own files without using any other logging framework. auditd logs aren't included in syslog either.