Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Just to update everyone on the nasty crash one of our servers continued having even after 5.5/5.6, I posted a summary of the results here: https://bugzilla.redhat.com/show_bug.cgi?id=1690769#c4. Sincerely, Artem -- Founder, Android Police , APK Mirror

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Good morning, looks like on 2 clients there was an automatic cleanup: [2019-03-21 05:04:52.857127] I [fuse-bridge.c:5144:fuse_thread_proc] 0-fuse: initating unmount of /data/repository/shared/public [2019-03-21 05:04:52.857507] W [glusterfsd.c:1500:cleanup_and_exit]

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Amar, I see debuginfo packages now and have installed them. I'm available via Skype as before, just ping me there. Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi, i updated our live systems (debian stretch) from 5.3 -> 5.5 this morning; update went fine so far :-) However, on 3 (of 9) clients, the log entries still appear. The upgrade steps for all clients were identical: - install 5.5 (via apt upgrade) - umount volumes - mount volumes Interestingly

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

On Wed, Mar 20, 2019 at 9:52 AM Artem Russakovskii wrote: > Can I roll back performance.write-behind: off and lru-limit=0 then? I'm > waiting for the debug packages to be available for OpenSUSE, then I can > help Amar with another debug session. > > Yes, the write-behind issue is now fixed. You

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Can I roll back performance.write-behind: off and lru-limit=0 then? I'm waiting for the debug packages to be available for OpenSUSE, then I can help Amar with another debug session. In the meantime, have you had time to set up 1x4 replicate testing? I was told you were only testing 1x3, and it's

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi Artem, I think you are running into a different crash. The ones reported which were prevented by turning off write-behind are now fixed. We will need to look into the one you are seeing to see why it is happening. Regards, Nithya On Tue, 19 Mar 2019 at 20:25, Artem Russakovskii wrote: >

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

The flood is indeed fixed for us on 5.5. However, the crashes are not. Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii | @ArtemR

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi Amar, if you refer to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1674225 : in the test setup i haven't seen those entries, while copying & deleting a few GBs of data. For a final statement we have to wait until i updated our live gluster servers - could take place on tuesday or

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi Hu Bert, Appreciate the feedback. Also are the other boiling issues related to logs fixed now? -Amar On Mon, Mar 18, 2019 at 3:54 PM Hu Bert wrote: > update: upgrade from 5.3 -> 5.5 in a replicate 3 test setup with 2 > volumes done. In 'gluster peer status' the peers stay connected during

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

update: upgrade from 5.3 -> 5.5 in a replicate 3 test setup with 2 volumes done. In 'gluster peer status' the peers stay connected during the upgrade, no 'peer rejected' messages. No cksum mismatches in the logs. Looks good :-) Am Mo., 18. März 2019 um 09:54 Uhr schrieb Hu Bert : > > Good morning

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Good morning :-) for debian the packages are there: https://download.gluster.org/pub/gluster/glusterfs/5/5.5/Debian/stretch/amd64/apt/pool/main/g/glusterfs/ I'll do an upgrade of a test installation 5.3 -> 5.5 and see if there are some errors etc. and report back. btw: no release notes for 5.4

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

We created a 5.5 release tag, and it is under packaging now. It should be packaged and ready for testing early next week and should be released close to mid-week next week. Thanks, Shyam On 3/13/19 12:34 PM, Artem Russakovskii wrote: > Wednesday now with no update :-/ > > Sincerely, > Artem > >

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Wednesday now with no update :-/ Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii | @ArtemR On Tue,

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi Amar, Any updates on this? I'm still not seeing it in OpenSUSE build repos. Maybe later today? Thanks. Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

We are talking days. Not weeks. Considering already it is Thursday here. 1 more day for tagging, and packaging. May be ok to expect it on Monday. -Amar On Thu, Mar 7, 2019 at 11:54 AM Artem Russakovskii wrote: > Is the next release going to be an imminent hotfix, i.e. something like >

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Is the next release going to be an imminent hotfix, i.e. something like today/tomorrow, or are we talking weeks? Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Ended up downgrading to 5.3 just in case. Peer status and volume status are OK now. zypper install --oldpackage glusterfs-5.3-lp150.100.1 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: glusterfs-5.3-lp150.100.1.x86_64 requires libgfapi0 = 5.3,

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Noticed the same when upgrading from 5.3 to 5.4, as mentioned. I'm confused though. Is actual replication affected, because the 5.4 server and the 3x 5.3 servers still show heal info as all 4 connected, and the files seem to be replicating correctly as well. So what's actually affected - just

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

fyi: did a downgrade 5.4 -> 5.3 and it worked. all replicas are up and running. Awaiting updated v5.4. thx :-) Am Di., 5. März 2019 um 09:26 Uhr schrieb Hari Gowtham : > > There are plans to revert the patch causing this error and rebuilt 5.4. > This should happen faster. the rebuilt 5.4 should

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

There are plans to revert the patch causing this error and rebuilt 5.4. This should happen faster. the rebuilt 5.4 should be void of this upgrade issue. In the meantime, you can use 5.3 for this cluster. Downgrading to 5.3 will work if it was just one node that was upgrade to 5.4 and the other

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi Hari, thx for the hint. Do you know when this will be fixed? Is a downgrade 5.4 -> 5.3 a possibility to fix this? Hubert Am Di., 5. März 2019 um 08:32 Uhr schrieb Hari Gowtham : > > Hi, > > This is a known issue we are working on. > As the checksum differs between the updated and non updated

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi, This is a known issue we are working on. As the checksum differs between the updated and non updated node, the peers are getting rejected. The bricks aren't coming because of the same issue. More about the issue: https://bugzilla.redhat.com/show_bug.cgi?id=1685120 On Tue, Mar 5, 2019 at

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Interestingly: gluster volume status misses gluster1, while heal statistics show gluster1: gluster volume status workdata Status of volume: workdata Gluster process TCP Port RDMA Port Online Pid

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Hi Miling, well, there are such entries, but those haven't been a problem during install and the last kernel update+reboot. The entries look like: PUBLIC_IP gluster2.alpserver.de gluster2 192.168.0.50 gluster1 192.168.0.51 gluster2 192.168.0.52 gluster3 'ping gluster2' resolves to LAN IP; I

Re: [Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

There are probably DNS entries or /etc/hosts entries with the public IP Addresses that the host names (gluster1, gluster2, gluster3) are getting resolved to. /etc/resolv.conf would tell which is the default domain searched for the node names and the DNS servers which respond to the queries. On

[Gluster-users] Upgrade 5.3 -> 5.4 on debian: public IP is used instead of LAN IP

Good morning, i have a replicate 3 setup with 2 volumes, running on version 5.3 on debian stretch. This morning i upgraded one server to version 5.4 and rebooted the machine; after the restart i noticed that: - no brick process is running - gluster volume status only shows the server itself: