[04:47] Hi guys, I was looking into why logwatch for my NAS wasn't reporting zfs info and I noticed that the zz-zfs.conf service script for logwatch presumes the zfs and zpool binaries are in /usr/sbin while zfsonlinux in 16.04 installs those in /sbin/, should I file this as a logwatch bug or a zfsonlinux bug on launchpad? [07:59] Bert_2: sounds like a logwatch bug to me === JanC_ is now known as JanC [11:24] I need some help. [11:24] I can't connect to my server on a client PC, even thought apt update and local SSH-ing work fine. [11:43] Hello? [11:49] define can't connect [11:55] Cygwin says: "Could not resolve hostname : Name or service not known". [11:56] ok - so there is no dns entry for it [11:56] so this system has a name resolution issue [11:56] cygwin....ugh [11:56] not an ubuntu issue [11:56] WinSCP also reports the same issue. [11:57] you have no name server resoution for your ubuntu IP [11:57] How do I alleviate that issue? [11:58] fix whatever your name service is [11:58] or put an entry in the hostfile on the client [11:58] How? [11:58] or connect to the servers' ip address , not hostname [11:58] Oh. [11:58] BTW, how do I check my IP address on the server? [11:58] ip a [12:02] Now it says "Connection refused". [12:13] Which IP address should I connect to? [12:16] the one the service your are trying to connect to listens on [12:17] "netstat" -pn or "lsof -i" would show. [12:32] Which IP address, to be exact? [12:37] how would we know? [12:39] you are trying to connect, using an unknown protocol, from some client (ip address unknown) to some service (unknown) listening on some (unknown) port on a server running ubuntu using an unknown protocol. it is unknown which network the client and the server reside in, and how connectivity between them can be established. [12:39] so, without more details from your end, no one will be able to help you. [12:43] The server and the client reside in the same home network. [12:43] I can upload a photo if you want. [12:48] https://s19.postimg.org/51wl94vsj/lsof_-i_output.jpg [12:49] BTW, how can I scroll text in the non-desktop terminal? [12:50] Ie., the one that you open with Alt+1-Alt+6. [13:14] Hello? [13:15] did you try the PgUp/PgDn keys? [13:18] They don't work and PgDn only yields me a tilde sign. [13:20] Shift+PgUp/PgDn should work [13:22] It works! [13:34] But still, what am I supposed to do? [13:37] is sshd running at your server? check i.e. with netstat -tlp | grep sshd [13:43] https://s19.postimg.org/4b8gh0y7n/20171105_144153.jpg [13:43] The command's output. [13:48] what does /var/log/auth.log tells about connection refused? [13:50] On the client? [13:50] on the server [13:50] May I post a picture of it? [13:52] yes [13:53] Or you know what? I'll just upload it on hastebin. [14:01] https://hastebin.com/uyuwucerix.sql [14:05] Can't see any ssh connection from your client. Did you try to ssh via ip address from your client? [14:12] When I try connecting to the CORRECT IP address, on the correct port, it says "Connection timed out". [14:16] that means your client cannot access your server at port 22/tcp. Do you get an replay for ping from client to server? [14:16] reply [14:17] How do I ping it? [14:17] With cmd? [14:18] cmd: ping [14:18] The host is unreachable. [14:20] can you ping any other machine i.e. router from your client and your server? [14:23] I can ping my router just fine. [14:28] ping server to router is ok, ping from server to client any vice versa is not? [14:33] Ping to router from client AND server are both fine. [14:33] Let me try server->client. [14:34] That works just fine. [14:34] How do I stop the pinging process? [14:35] CTRL+C [14:36] do you have any kind of firewall configured on the server? [14:37] No. [14:37] check iptables -L -n [14:37] On server? [14:37] yes [14:38] last idea: do all machines have the same netmask? [14:38] How do I check it? [14:41] ip a [14:44] https://s19.postimg.org/y0ln9fetf/20171105_154331.jpg [14:48] are client or server connected via WLAN? [14:49] and if so, does your router (access point) allow communication between clients? [15:06] this is getting silly [15:06] why is someone trying to run a server who doesn't understand basic networking [15:11] The client is connected through Ethernet, and the server through a wireless adapter. [15:12] MartesZibellina: have you got a basic grasp of IP networking [15:21] I just want my problem to be solved. [15:22] MartesZibellina: I understand that, that's why I'm asking if you understand basic TCP IP networking [15:27] I don't think so. [15:27] ok - so why are you trying to run a server ? [15:28] I want to make an use of my old PC. [15:28] Why would it be only lying around, after all? [15:28] The SSH worked just fine before rebooting. [15:28] then I suggest you research a basic understanding of networking [15:29] Are there any good sites? [15:30] just buy a book === Isla_de_Muerte is now known as NwS [16:36] Maybe removing desktop environments will help? [16:41] Also, there's "A job is starting for Wait for Network to be Configured". [16:41] And it fails. [16:41] Upon boot. [17:09] MartesZibellina: again, this is why you need basic understanding of networking [17:30] Now, the problem's solved! [17:31] It's the desktop environment that's been interfering with the server! [17:40] what ? [17:44] Now I can SSH just fine. [17:44] the desktop does not touch ssh [17:45] Maybe the network manager did. [17:45] if you have configured /etc/interfaces and network manager then of course it will fight [17:45] as both are trying to manage the network card [17:50] In any case, now I can rest assured that my client will SSH just fine to the server. [17:50] I installed lubuntu-desktop before. === Jynxie_ is now known as Jynxie === markthomas_ is now known as markthomas === techmagus_ is now known as techmagus === teward_ is now known as teward === duxklr is now known as jemurray === stgraber_ is now known as stgraber