| mmercer | hey guys, im working on repackaging python-pi, since the version in ubuntu16 has a few errors, i just want to patch that version and increment the minor string, but i cant find any documentation on how to do this | 00:39 |
|---|---|---|
| mmercer | ive used apt-get source to get the source file, ive used dpkg-source but i cant figure out how to actually change the version number before recompiling | 00:45 |
| mmercer | nvm, figured it out | 01:18 |
| Triffid_Hunter | hi, how do I stop networkmanager changing the metric on my routes, or at least tell it what metric it should use? | 06:24 |
| Triffid_Hunter | oh actually it seems to be systemd-networkd | 06:26 |
| === jelly-home is now known as jelly | ||
| === Ussat-1 is now known as Ussat | ||
| cpaelzer | ahasenack: why does libpmemobj-cpp need the libpmemobj-dev dependency to be versioned? | 14:50 |
| cpaelzer | I see that debian didn't take the change that you had, but took all others | 14:50 |
| ahasenack | cpaelzer: readme says it should work with >= 1.4 or 1.5, iirc | 14:50 |
| ahasenack | but then why is the build-depends on 1.6 | 14:51 |
| cpaelzer | and I wondered as I have seen other packages with versioned build-depends but non-versioned depends on the -dev package | 14:51 |
| ahasenack | so I added that same depends | 14:51 |
| ahasenack | this is existing delta, btw | 14:51 |
| cpaelzer | I know | 14:51 |
| cpaelzer | I jstu wondered this being the last that is elft if it could be a sync | 14:51 |
| ahasenack | I think this stuff is still a bit experimental | 14:52 |
| ahasenack | but I could drop it next time | 14:52 |
| cpaelzer | oh yeah it seems that way | 14:52 |
| cpaelzer | well, you could upgrade from Bionic and update one, but not the other without your change | 14:52 |
| cpaelzer | so I see some (minor) reson to keep it | 14:52 |
| cpaelzer | thanks for talking about it, I mostly wanted to know if there was more to it that I could learn and then fix in other packages | 14:52 |
| ahasenack | and debian didn't have that package back then | 14:52 |
| ahasenack | so they don't have this concern of upgrading from 1.4.1 | 14:53 |
| V7 | Hey all | 18:52 |
| V7 | Could anyone suggest how to get rid of systemd-resolve's messages in syslog like: https://termbin.com/u2ym | 18:52 |
| V7 | Already relinked /etc/resolv.conf and reinstalled resolvconf | 18:52 |
| lordcirth | V7, why are you trying to disable systemd-resolve? | 18:54 |
| V7 | I'm not trying to disable it | 18:54 |
| V7 | Why do you think like that? | 18:54 |
| lordcirth | Well, doesn't resolvconf conflict with it? | 18:54 |
| V7 | I'm just trying to figure out why does it produce so much restarts | 18:54 |
| V7 | lordcirth: Don't know. Could it? | 18:55 |
| nacc | V7: there is only one restart listed. | 18:55 |
| V7 | nacc: It's about each 3 minutes | 18:55 |
| nacc | V7: ... how would we know that from the log you pasted? | 18:55 |
| V7 | ~ Same message | 18:55 |
| V7 | Sorry | 18:55 |
| lordcirth | Both try to manage /etc/resolv.conf. IIRC systemd-resolve disables itself if resolvconf is installed? Not sure | 18:55 |
| V7 | /etc/resolv.conf is linek to /run/resolvconf/resolv.conf | 18:57 |
| V7 | linked* | 18:57 |
| V7 | Currently, it contains https://termbin.com/9ho6 | 18:58 |
| lordcirth | Ok, so resolvconf is directing DNS to systemd-resolve. | 18:59 |
| V7 | So any ideas :)? | 19:12 |
| lordcirth | Personally I don't see why the log lines are an issue. | 19:13 |
| nacc | V7: can you show us actual logging that indicates it is restarting repeatedly? | 19:14 |
| V7 | It's flooding it | 19:14 |
| V7 | Roger that | 19:14 |
| V7 | nacc: https://termbin.com/y8o2 | 19:35 |
| nacc | V7: your system is getting an IP every 3 minutes | 20:03 |
| nacc | V7: so of course name resolution refreshs | 20:03 |
| V7 | How does it getit then? | 20:03 |
| nacc | V7: sorry? how does what get what? | 20:04 |
| V7 | How does a server get an ip every 3 minutes | 20:04 |
| nacc | V7: it's making a DHCP request (per your logs) to do so. | 20:05 |
| V7 | Every 3 minutes? | 20:06 |
| nacc | V7: I don't know if your lease is expiring rapidly, if your client is misconfigured | 20:06 |
| nacc | V7: yes, see the lines starting `dhclient: ` | 20:06 |
| V7 | Of you mean a DHCP server's lease might be to short | 20:06 |
| V7 | I'll check that | 20:06 |
| nacc | `dhclient[1309]: bound to 192.168.1.100 -- renewal in 226 seconds.` | 20:07 |
| nacc | that's about 3.75 minutes | 20:07 |
| nacc | which is absurdly short :) | 20:07 |
| GivenToCode | xpost from ubuntu: anyone run ubuntu 18.04 via community AMIs on EC2? I am seeing shutdown (stop/terminate) hang for about 4 minutes without any shutdown hooks activating on the instance (ie systemd) and then ec2 forcing termination | 20:09 |
| GivenToCode | i tried turning on systemd debugging but it appears whatever is hanging is hanging before all that | 20:10 |
| GivenToCode | I can say change in behavior happened sometime between July 29th at 2:10pm ET and Aug 1st 3:40pm ET | 20:10 |
| V7 | So, took a lok into mikrotik's configs | 20:19 |
| V7 | lease time was set to 10 minuts | 20:19 |
| V7 | minutes* | 20:19 |
| V7 | https://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server#Lease_Store_Configuration | 20:19 |
| V7 | A page claims that after half of this time client might ask for renewal might this be a causer of log write? | 20:19 |
| V7 | renewal. Might* | 20:20 |
| lordcirth | Yes, renew at 1/2 is standard. The question is, why is the DHCP server giving 6 minute leases? | 20:38 |
| lordcirth | ~24 hours is more standard. | 20:38 |
| V7 | Already changed to normal | 20:40 |
| V7 | Thank you very much | 20:40 |
| V7 | Waiting for new entries in logs | 20:40 |
| V7 | Do these logs look normal? | 20:41 |
| V7 | Btw | 20:41 |
| V7 | Is it okay to add IPs to hosts.deny if it attacks SMTP server? | 21:35 |
| tomreyn | sure, though firewalling may be a better approach. | 21:44 |
| tomreyn | it may not be desirable if there's also legitimate (smtp or other) traffic coming from there, though. | 21:45 |
| V7 | Thank you very much | 21:46 |
| tomreyn | e.g. you wouldn't want to firewall legitimate (ham) mail servers which also send spam, handle them via SMTP instead. | 21:48 |
| tomreyn | if it's only smtp auth brute forcing, though... firewall it. | 21:49 |
| tomreyn | keep in mind, though, that ip addressing keeps changing, so don't block ip addresses forever. | 21:49 |
| V7 | Roger that | 21:54 |
| RoyK | V7: tcpwrapper as in hosts.{deny,allow} isn't used much these days | 22:13 |
| V7 | Roger that | 22:13 |
| RoyK | fail2ban can be nice too if configured correctly | 22:16 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!