New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mount.nfs: portmap query failed: RPC: Remote system error - Address already in use #3045
Comments
@exfarmer
the same mount comand works two times A blind guess (I am not at all a NFS expert):
the third mounting happens directly (less than 0.2 seconds) after To verify if it is a timing issue on your NFS server
and retry "rear mkbackup" to check if it works now more reliably. |
Hi,
The mount point is set for timeo=600, that’s 60 seconds.
This is also the default.
The NFS command is also a hard mount, so changing the timeout value has no effect.
I need to investigate soft mounts and timeout values. For example:
What’s the disadvantage or what could go wrong if this is a NFS soft mount?
Do you have any guidance on this?
|
I am not at all a sufficient NFS expert |
Hi,
Is there a rear policy on this?
|
@exfarmer ReaR follows what you define with |
Let me ask another question.
I added this line to the local.conf file:
PROGRESS_WAIT_SECONDS="10"
But the log still shows the archive growing every 1-2 seconds.
I thought that change in the local.conf file would mean the updates come every 10 seconds or more.
|
@exfarmer
and
Messages in the log file are not affected by PROGRESS_WAIT_SECONDS. |
@exfarmer not using '-v' (verbose) option might help |
@exfarmer rpcinfo -p edlussp001.oneabbott.com should show you what the NFS server supports |
Regarding verbose messages in the log file: |
@gdha On the other hand I wonder why it actually matters |
Hi,
The tar verbose messages fill the log message buffer when running the rear backup in BladeLogic.
I will change the level on a few servers and see what happens.
Thank you
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Johannes Meixner ***@***.***>
Sent: Thursday, October 5, 2023 6:17:53 AM
To: rear/rear ***@***.***>
Cc: Hess, Gary ***@***.***>; Mention ***@***.***>
Subject: Re: [rear/rear] mount.nfs: portmap query failed: RPC: Remote system error - Address already in use (Issue #3045)
EXTERNAL EMAIL: Only click links or open attachments if you recognize the sender and know the content is safe.
@gdha<https://urldefense.com/v3/__https://github.com/gdha__;!!BBM_p3AAtQ!KT2SKogLxds0vBYUbVg4OmfxSpceFpr24hUr0sOiPKNF4zTluei9ndd1Jaf_9wMfv50pyVNJzpuTVx-W-c6nH2cZ$>
yes - perhaps - but I don't know if there is a reason
why the 'tar' option '--verbose' is hardcoded.
On the other hand I wonder why it actually matters
when there are verbose 'tar' messages in the log file.
I understand the need for configurable verbosity level
on the terminal - but why does the log file actually matter?
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/rear/rear/issues/3045*issuecomment-1748600710__;Iw!!BBM_p3AAtQ!KT2SKogLxds0vBYUbVg4OmfxSpceFpr24hUr0sOiPKNF4zTluei9ndd1Jaf_9wMfv50pyVNJzpuTVx-W-b6a0Toy$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ASRDKRITOGX5BIOZD2EC74DX52CNDAVCNFSM6AAAAAA4KTEIFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBYGYYDANZRGA__;!!BBM_p3AAtQ!KT2SKogLxds0vBYUbVg4OmfxSpceFpr24hUr0sOiPKNF4zTluei9ndd1Jaf_9wMfv50pyVNJzpuTVx-W-Wp0dcZb$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@exfarmer Normally we call commands in verbose mode |
Hi,
Like so many of the comments in the links you sent.
I feel the need for verbose messages, but not for tar.
On another note: do you know if rear supports NFS v4?
Thank you
|
Yes it does. |
Thank you
|
Hi,
I changed the /usr/share/rear/backup/NETFS/default/50_make_backup.sh script to remove –verbose in the tar command:
Line 75: Log $BACKUP_PROG $TAR_OPTIONS --sparse --block-number --totals –verbose \
Line 82: Log $BACKUP_PROG $TAR_OPTIONS --sparse --block-number --totals –verbose \
These are the same without –verbose on the end, but that didn’t remove the verbose output in the logs.
I want verbose messages for all other commands, just not for tar.
We maybe running an older version of rear, Relax-and-Recover 1.17.2 / Git, so I figured the command was 50_make_backup.sh and not 500_make_backup.sh
The servers ( I tested on 2 servers ) are RHEL v6.
Thank you
Abbott
[image001]
Gary Hess
Administrator, Sr - Unix
Abbott
|
@exfarmer Rear version 1.17.2 is no longer supported by us (nor by RH I suppose). However, you can still use a more recent version from http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/RHEL_6/ |
Stale issue message |
Regarding I will have a look (as time permits) if it works for me I guess the reason why the 'tar' option '--verbose' is hardcoded Alternative methods could be |
Hi,
I need to stop the tar progress messages during execution.
That output isn’t in the /var/log/rear log file anyway.
The final tar status is important and is needed.
Is there a way I can do that with the BACKUP_PROG_OPTIONS now,
or does it require an enhancement?
There are 985 lines:
Info 11/30/2023 21:52:58 Archived 2996 MiB [avg 3068 KiB/sec] 7 [2K
Info 11/30/2023 21:52:57 Archived 2996 MiB [avg 3071 KiB/sec] 7 [2K
Info 11/30/2023 21:52:56 Archived 2996 MiB [avg 3074 KiB/sec] 7 [2K
Info 11/30/2023 21:52:55 Archived 2996 MiB [avg 3077 KiB/sec] 7 [2K
…
…
Info 11/30/2023 21:36:24 Archived 37 MiB [avg 6481 KiB/sec] 7 [2K
Info 11/30/2023 21:36:23 Archived 31 MiB [avg 6409 KiB/sec] 7 [2K
Info 11/30/2023 21:36:22 Archived 24 MiB [avg 6196 KiB/sec] 7 [2K
Info 11/30/2023 21:36:21 Archived 17 MiB [avg 6048 KiB/sec] 7 [2K
These are not needed unless I run the job manually.
Thank you
Abbott
|
Ah! Those messages are from the so called "progress subsystem",
Currently there is no way to configure Currently we have |
There’s the issue.
Abbott
[image001]
Gary Hess
Administrator, Sr - Unix
Abbott
253 Financial Blvd.
Liberty, SC 29657 USA
O:
+1 864-843-8352
M:
+1 864-546-8921
E:
***@***.******@***.***>
From: Johannes Meixner ***@***.***>
Sent: Thursday, December 7, 2023 9:02 AM
To: rear/rear ***@***.***>
Cc: Hess, Gary ***@***.***>; Mention ***@***.***>
Subject: Re: [rear/rear] mount.nfs: portmap query failed: RPC: Remote system error - Address already in use (Issue #3045)
EXTERNAL EMAIL: Only click links or open attachments if you recognize the sender and know the content is safe.
Ah!
Those messages are from the so called "progress subsystem",
e.g. in usr/share/rear/backup/NETFS/default/500_make_backup.sh
ProgressStart "Preparing archive operation"
...
ProgressInfo "Archived $((size/1024/1024)) MiB [avg $((size/1024/(SECONDS-starttime))) KiB/sec] "
...
ProgressStop
Currently there is no way to configure
to not get those messages.
Currently we have
PROGRESS_MODE "ANSI" (default/fallback) or "plain"
but we do not have e.g. PROGRESS_MODE "none" or "quiet".
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/rear/rear/issues/3045*issuecomment-1845395986__;Iw!!BBM_p3AAtQ!KtauRK2QmbN9CmMtbt6Z_pnFNTeK8NMl4BF9UwOp4aX5lgE4PsTVlQLOyUUJmWqB04D2w89tXOo8XZSCfNSqH-z6$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASRDKRKFCNLFGWNY2UWRSS3YIHD5JAVCNFSM6AAAAAA4KTEIFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVGM4TKOJYGY__;!!BBM_p3AAtQ!KtauRK2QmbN9CmMtbt6Z_pnFNTeK8NMl4BF9UwOp4aX5lgE4PsTVlQLOyUUJmWqB04D2w89tXOo8XZSCfB-Tm0Qq$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Stale issue message |
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.4 / Git
If your ReaR version is not the current version, explain why you can't upgrade:
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Red Hat Enterprise Linux Server release 7.9 (Maipo)
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
VMware, Inc. VMware Virtual Platform
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
SAN
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
Workaround, if any:
None
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
rear-ussp-oaddvic02.log
You can drag-drop log files into this editor to create an attachment
or paste verbatim text like command output or file content
by including it between a leading and a closing line of
three backticks like this:
The text was updated successfully, but these errors were encountered: