Rpc error unable to receive

Rpc error unable to receive Привет всем! ОС Linux RH 7.2 . На удаленной машине запущены portmap и nfs демоны, в /etc/exports прописана строчка вида /disk/ 192.168.3.5(rw,all_squash) изначально пробовал без all_squash со стороны клиента набираю mount -t nfs 192.168.3.2:/disk/ /mnt/net/ mount: RPC : Unable to receive; errno = Connection refused Cамое интересное что с […]

showmount -e
mount clntudp_create: RPC: Program not registered

Источник

Troubleshooting common NFS issues in Linux

The post discusses most commonly occurring NFS issues in Linux and how to resolve them.

1. Error: “Server Not Responding”

The Network File System (NFS) client and server communicate using Remote Procedure Call (RPC) messages over the network. Both the host->client and client->host communication paths must be functional. Use common tools such as ping, traceroute or tracepath to verify that the client and server machines can reach each other. If not, examine the network interface card (NIC) settings using either ifconfig or ethtool to verify the IP settings.

The NFS file system also reports “server not responding” when a heavy server or network loads cause the RPC message responses to time out. Use the “timeo=N” mount option on the client to increase the timeout. Check “man mount” for more information.

2. Error: “No route to host”

The “no route to host” error can be reported when the client attempts to mount an NFS file system, even if the client can successfully ping the server:

This can be caused by the RPC messages being filtered by either the host firewall, the client firewall, or a network switch. Verify if a firewall is active and if NFS traffic is allowed. Normally nfs is using port 2049. As a quick test one can switch the firewall off by:

on both the client and the server. Try mounting the NFS directory again. Do not forget to switch it back on and configure it correctly to allow NFS traffic/

3. Error: “mount clntudp_create: RPC: Port mapper failure – RPC: Unable to receive”

The Linux NFS implementation requires that both the NFS service and the portmapper (RPC) service be running on both the client and the server. Check it like this:

If not, start it with the commands give below.

4. Error: “NFS Stale File Handle”

A program uses the open(2) system call to access an NFS file in the same way the application opens a local file. This system call returns a file descriptor, or “handle”, that the program subsequently uses in I/O commands to identify the file to be manipulated.

Unlike traditional Linux file systems that allow an application to access an open file even if the file has been deleted using unlink or rm, NFS does not support this feature. An NFS file is deleted immediately. Any program which attempts to do further I/O on the deleted file will receive the “NFS Stale File Handle” error. For example, if your current working directory is an NFS directory and is deleted, you will see this error at the next shell prompt.

To refresh the client’s state with that of the server you may forcely unmount the mount point:

or kill the process, which references the mounted file system:

5. Error: “Access Denied” or “Permission Denied”

Check the export permissions for the NFS file system. You can do this from the client:

If you see unexpected export permissions, check the /etc/exports file on the server. Make sure there is no syntax error such as space between the permitted host and the permissions. There is a significant difference in the line:

because the second exports /home read-write to all systems: not what was intended. Note that the line still has correct syntax, so NFS will not complain about it.

6. Error: “rpc mount export: RPC: Timed out”

This is caused by DNS name resolution issue. NFS(RPC) needs reverse name resolution. If NFS server or client cannot resolve their name, this error occurs. In case gets the error message, check DNS configuration and /etc/hosts configuration.

Источник

Maaz Anjum’s Blog

While trying to setup NFS on an OVM 3.2 configuration on OEL 5.9, I followed the documentation to the letter but when time came to start the NFS daemon I kept getting the error above.

After a little googling, it turns out that RPCBind may not be running.

Perhaps I needed to update my NFS Utility packages?

Then I tried the RPC info command again, but no luck!

Portmap? Oh, that would explain a lot since NFS apparently requires port mapper service to run.

Try RPC info again. Aha, that did it!

Finally, restart the NFS Service and set it to autostart.

Hope this was helpful!

Like this:

Related

21 comments

I ran into the same issue for my rhel6 box. I followed your instructions. “portmap” service was not available in my service. Instead Rhel6 has rpcbind service. Once I started rpbcbind service <“service rpcbind start”], I was able to start the nfs service.
Thanks for such a detailed instruction.

I am glad the instructions were helpful and thank you for sharing your fix on RHEL6!

Thanks Maaz –
I ran into this same issue setting up Oracle VM Manager/Servers in virtualbox. I was following the documentation here: http://www.oracle.com/technetwork/server-storage/vm/ovm3-demo-vbox-1680215.pdf
Steve

I was working through the same document. Thanks for the mention on twitter 🙂

Yey! For CentOS 6.5 the service you start/enable before nfs is called “rpcbind”.

Thanks for sharing your experience on CentOS!

It’s hard to find your articles in google. I found it on 18 spot,
you should build quality backlinks , it will help you to increase traffic.
I know how to help you, just type in google – k2 seo tricks

Can confirm your fix worked on RHEL 5.10. It’s true that RHEL 6 has rpcbind instead. Thanks for the post!

I haven’t tried it on RHEL 5.10, but I’d be curious to know whether the solution is the same or different.

Glad it helped you in any case 🙂

RHEL 5.10 was identical. I Googled the error and saw your post. I checked portmap and saw it was off, started it and nfs fired right up. Rebooting would have fixed it since in my case portmap was set to “on” in checkconfig. I did a brief RCA and found that an installer script I had been running killed nfs processes as part of its logic. The script failed for an unrelated reason then exited without sending the init.d startup commands. All is well and work is flowing, thanks again.

Your Article helped me too. Thanks!

Glad it helped PK!

When iam restarting the nfs service it showing me

Starting NFS quotas: Cannot register service: RPC: Unable to receive; errno = Connection refused
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
[FAILED]
Starting NFS mountd: [FAILED]
Starting NFS daemon: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
rpc.nfsd: unable to set any sockets for nfsd
===========================================
Even though ifollowed above step’s the portmap can’t restart even please can you help on this.

Mohan, what is your OS? Do you have iptables enabled?

Источник

Adblock
detector

If you are getting the below error while starting your NFS service, this tutorial will help you to fix the this error :

Error:

Cannot register service: RPC: Unable to receive; errno = Connection refused unable to register (NFS3_PROGRAM, NFS_V3, udp)

In this article I will show you how to fix the above error.

You will get this error if there is not rpcbind service not installed or not started on your server.

Check rpcbind is running or not if not running you will get below error:

# rpcinfo
rpcinfo: can't contact rpcbind: RPC: Remote system error - No such file or directory

Start rpcbind service on your sever and if not running.

# /etc/init.d/rpcbind start

After starting rpcbind check again.

# rpcinfo

You will get some output like below if running.

program version netid     address                service    owner
    100000    4    tcp6      ::.0.111               portmapper superuser
    100000    3    tcp6      ::.0.111               portmapper superuser
    100000    4    udp6      ::.0.111               portmapper superuser
    100000    3    udp6      ::.0.111               portmapper superuser
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /var/run/rpcbind.sock  portmapper superuser
    100000    3    local     /var/run/rpcbind.sock  portmapper superuser

Install rpcbind

If rpcbind is not installed on your server follow the below command to install it.

# yum -y install rpcbind
Loaded plugins: fastestmirror, security
Setting up Install Process
Loading mirror speeds from cached hostfile
 * epel: mirror.compevo.com
 * openvz-kernel-rhel6: mirror.steadfast.net
 * openvz-utils: mirror.steadfast.net
 * rpmforge: mirror.lstn.net
Resolving Dependencies
--> Running transaction check
---> Package rpcbind.x86_64 0:0.2.0-13.el6_9.1 will be installed
--> Processing Dependency: libgssglue for package: rpcbind-0.2.0-13.el6_9.1.x86_64
--> Processing Dependency: libtirpc.so.1()(64bit) for package: rpcbind-0.2.0-13.el6_9.1.x86_64
--> Running transaction check
---> Package libgssglue.x86_64 0:0.1-11.el6 will be installed
---> Package libtirpc.x86_64 0:0.2.1-13.el6_9 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================================================================================
 Package                           Arch                          Version                                   Repository                      Size
================================================================================================================================================
Installing:
 rpcbind                           x86_64                        0.2.0-13.el6_9.1                          updates                         51 k
Installing for dependencies:
 libgssglue                        x86_64                        0.1-11.el6                                base                            23 k
 libtirpc                          x86_64                        0.2.1-13.el6_9                            updates                         82 k

Transaction Summary
================================================================================================================================================
Install       3 Package(s)

Total download size: 156 k
Installed size: 312 k
Downloading Packages:
(1/3): libgssglue-0.1-11.el6.x86_64.rpm                                                                                  |  23 kB     00:00
(2/3): libtirpc-0.2.1-13.el6_9.x86_64.rpm                                                                                |  82 kB     00:00
(3/3): rpcbind-0.2.0-13.el6_9.1.x86_64.rpm                                                                               |  51 kB     00:00
------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                            18 MB/s | 156 kB     00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : libgssglue-0.1-11.el6.x86_64                                                                                                 1/3
  Installing : libtirpc-0.2.1-13.el6_9.x86_64                                                                                               2/3
  Installing : rpcbind-0.2.0-13.el6_9.1.x86_64                                                                                              3/3
  Verifying  : rpcbind-0.2.0-13.el6_9.1.x86_64                                                                                              1/3
  Verifying  : libgssglue-0.1-11.el6.x86_64                                                                                                 2/3
  Verifying  : libtirpc-0.2.1-13.el6_9.x86_64                                                                                               3/3

Installed:
  rpcbind.x86_64 0:0.2.0-13.el6_9.1

Dependency Installed:
  libgssglue.x86_64 0:0.1-11.el6                                        libtirpc.x86_64 0:0.2.1-13.el6_9

Complete!

Start rpcbind service after installing.

# /etc/init.d/rpcbind start

Thank you! for visiting LookLinux.

If you find this tutorial helpful please share with your friends to keep it alive.
For more helpful topic browse my website www.looklinux.com.
To become an author at LookLinux Submit Article.
Stay connected to Facebook.

You may also like

About the author

mm

Hi! I’m Santosh and I’m here to post some cool article for you. If you have any query and suggestion please comment in comment section.

I setup the NFS server without any issues.

On the NFS server, the following are already taken care:

  • rpcbind service is running.
  • nfs service is running.
  • I’ve exported a local directory using client-ip using exportfs


However, on the client side, when I do “showmount -e”, I got the following error message: “clnt_create: RPC: Port mapper failure – Unable to receive: errno 113 (No route to host)”

showmount output:

# showmount -e 192.168.101.1
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)

In the above case, that 192.168.101.1 is where the NFS server is running.

If you get the above, error message, go through the following check-list to identify the problem.

1. Check Connectivity between the server

From the NFS client machine, ping the NFS server ip-address to make sure it is working properly.

ping 192.168.101.1

If ICMP is disabled on the NFS server, do other appropriate checks to make sure you can connect to that server. May be you can ssh to it.

ssh 192.168.101.1

2. Execute portinfo

On the NFS client machine execute the following, which will display the RPC information of the remote NFS server.

# rpcinfo -p 192.168.102.23
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100011    1   udp    875  rquotad
    100005    1   udp  59353  mountd
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl
    100021    1   udp  34104  nlockmgr
    100021    3   udp  34104  nlockmgr
    ...

As you see from the above output, rpcinfo can talk to NFS server, and it also shows that NFS service is running on the NFS server.

If you don’t have the NFS server running, start it on the NFS server:

service nfs start

3. Open-up Appropriate Ports

Check if you are running IPTables on the NFS server.

service iptables status

If you are running IPTables, make sure you open-up port 111 and 2049 as shown below.

iptables -A INPUT -p tcp --dport 111 -j ACCEPT
iptables -A INPUT -p udp --dport 111 -j ACCEPT
iptables -A INPUT -p tcp --dport 2049 -j ACCEPT
iptables -A INPUT -p udp --dport 2049 -j ACCEPT

Also, please note that if you are running SELinux, by default it allows NFS to share the mount points. So, you don’t need to do anything specific to SELinux. But, if you like, you can check the audit.log file to make sure SELinux is not blocking anything related to NFS.

The post discusses most commonly occurring NFS issues in Linux and how to resolve them.

1. Error: “Server Not Responding”

The Network File System (NFS) client and server communicate using Remote Procedure Call (RPC) messages over the network. Both the host->client and client->host communication paths must be functional. Use common tools such as ping, traceroute or tracepath to verify that the client and server machines can reach each other. If not, examine the network interface card (NIC) settings using either ifconfig or ethtool to verify the IP settings.

The NFS file system also reports “server not responding” when a heavy server or network loads cause the RPC message responses to time out. Use the “timeo=N” mount option on the client to increase the timeout. Check “man mount” for more information.

2. Error: “No route to host”

The “no route to host” error can be reported when the client attempts to mount an NFS file system, even if the client can successfully ping the server:

# mount NFS-Server:/data /data_remote
mount: mount to NFS server 'NFS-Server' failed: System Error: No route to host.

This can be caused by the RPC messages being filtered by either the host firewall, the client firewall, or a network switch. Verify if a firewall is active and if NFS traffic is allowed. Normally nfs is using port 2049. As a quick test one can switch the firewall off by:

on both the client and the server. Try mounting the NFS directory again. Do not forget to switch it back on and configure it correctly to allow NFS traffic/

3. Error: “mount clntudp_create: RPC: Port mapper failure – RPC: Unable to receive”

The Linux NFS implementation requires that both the NFS service and the portmapper (RPC) service be running on both the client and the server. Check it like this:

# rpcinfo -p
  program vers proto   port
  100000    2   tcp    111  portmapper [portmap service is started.]
  100000    2   udp    111  portmapper
  100011    1   udp    881  rquotad
  100011    2   udp    881  rquotad
...
# service portmap status
portmap (pid 7428) is running...   [portmap service is started.]

If not, start it with the commands give below.

# chkconfig portmap on
# service portmap start

4. Error: “NFS Stale File Handle”

A program uses the open(2) system call to access an NFS file in the same way the application opens a local file. This system call returns a file descriptor, or “handle”, that the program subsequently uses in I/O commands to identify the file to be manipulated.

Unlike traditional Linux file systems that allow an application to access an open file even if the file has been deleted using unlink or rm, NFS does not support this feature. An NFS file is deleted immediately. Any program which attempts to do further I/O on the deleted file will receive the “NFS Stale File Handle” error. For example, if your current working directory is an NFS directory and is deleted, you will see this error at the next shell prompt.

To refresh the client’s state with that of the server you may forcely unmount the mount point:

# umount -f /mnt/mount_point

or kill the process, which references the mounted file system:

# fuser -k [mounted-filesystem]

5. Error: “Access Denied” or “Permission Denied”

Check the export permissions for the NFS file system. You can do this from the client:

# showmount -e server_name

or from server:

If you see unexpected export permissions, check the /etc/exports file on the server. Make sure there is no syntax error such as space between the permitted host and the permissions. There is a significant difference in the line:

and the line:

because the second exports /home read-write to all systems: not what was intended. Note that the line still has correct syntax, so NFS will not complain about it.

6. Error: “rpc mount export: RPC: Timed out”

Error message:

Unable to access file system at [NFS SERVER]: rpc mount export: RPC: Timed out

This is caused by DNS name resolution issue. NFS(RPC) needs reverse name resolution. If NFS server or client cannot resolve their name, this error occurs. In case gets the error message, check DNS configuration and /etc/hosts configuration.

Comments

@webodan

monkeypox

added a commit
that referenced
this issue

Mar 11, 2020

@monkeypox

#1 make the volume popup progress bar smaller

#2 adopt library_show_genres var name

#3 get rid of unneeded divs in genre & artist columns

#4 add -art suffix to tag cover art album name

#5 fix #total time breakage

#6 fix tag view quick index breakage

#7 use "fast" fade animation for alerts + center text + give them a bit more padding + adjust top for mobile

#8 adjust knob vol buttons css

#9 adjust toggle buttons css

#10 ellipsis limited album & artist name, may need more work

monkeypox

added a commit
that referenced
this issue

Mar 12, 2020

@monkeypox

#1 take 2 ellipsis madness

#2 test using a css var for li width with eye towards a possible pref to set number of columns.

#3 change modal backdrop opacity to 1 in css since it already has an opacity, set the lower value in the computed color instead (in btnbarfix)

#4 add some padding-top to the alert second text line which I noticed because of the appearance library stuff but iirc we can just reload the library rather than refresh, and around half of the options don't need to even do that.

#5 take 2 knob fix wrt bloom

#6 remove filter icon from tag view album header

#7 last minute but seems ok, add limited class to the ul instead of the individual li elements, this way we save a bunch of memory and we can switch on the fly when I get around to making library options not always auto-refresh.

monkeypox

added a commit
that referenced
this issue

Mar 12, 2020

@monkeypox

#1 add missing menu lists to footer.php

#2 knob padding adjustment

#3 test adding thumb size as css var, regular as well as mobile now, e.g. --thumbcols is 18vw which is 5 columns, setting it to 10vw is 7

#4 change to adding limited class to #library-panel, all .lib-entry items are now supported.

#5 redid ellipsis css & simplified css a bit for tag & cover view in general

#6 messed with context-menu width a bit to try to work around dumb apple bug, 1080p+ uses em width, maybe

#7 added back lib search reset click handler, embiggened the button size, fixed the position, made it not dismiss the menu and refocused the input

monkeypox

added a commit
that referenced
this issue

Mar 13, 2020

@monkeypox

#1 adjust thumbcols to show 5 columns for landscape

#2 tag view no covers was showing the artist/year, make it not do that & adjust line-height.

#3 fix bug (?) in pnotify js where it wasn't hiding the second line div if there was no text.

#4 change to reload library instead of refresh page on library changes

#5 change show genres & ellipsis don't even need that so they now take effect immediately

#6 add test to the enter conditional on library search so a non-number will now bypass the rangify code and instead dismiss the menu & blur input (hide onscreen keyboard)

monkeypox

added a commit
that referenced
this issue

Mar 16, 2020

@monkeypox

#1 migrate missing bootstrap.min.css changes

#2 fix radio cover size to use var(--thumbcols)

#3 revert 2x width for playbar cover

#4 use rem for playbar button margin/padding.

#5 add configurable extra metadata, currently the string is a global, it'll need ui in the appearance panel (other options?) and either need a new session var or some fancy coding

#6 commented out (probably) unneeded screen saver things

#7 added countup & countdown support for the playbar progress in synctimers

#8 use radiocover/radiolist in setcv instead of just radio (oops)

#9 change id to match css for the mobile volume popup "progress" bar.

monkeypox

added a commit
that referenced
this issue

Mar 17, 2020

@monkeypox

#1 first stab at making config screens not do line splitting on mobile.

#2  adjust spacing for mobile wrt modals to better fit on smaller devices

#3 adjust how we display thumbs a bit wrt padding/margins

#4 fix font size on config screens

#5 add noscroll class to body when a modal is shown so the background doesn't scroll, this needed an edit of bootstrap.min.css so it needs to be re-minified for shipping versions.

#6 added a V button to minimize the playback screen on the top left

#7 modified how we display the m menu a little, also moved it in a touch

#8 inline-block made the year drop off the same line as the artist if it wasn't ellipsis limited so there are now separate display settings for both styles

#9 misc things

monkeypox

added a commit
that referenced
this issue

Mar 19, 2020

@monkeypox

#1 modify cover size on shorter big screen mobile devices (e.g. Galaxy 5).

#2 adjust play control buttons a bit (goes with above to provide more space between cover, controls and text).

#3 revert coverview playlist to normal size to prevent it from possibly overlapping the knob(s).

#4 prevent knob changing if volume is disabled.

#5 disable mute if knob track is touched and then act on touch.

#6 ditto volume buttons.

#7 remove some deprecated ssvolume references I noticed.

#8 fix menu header to display "Albums by [artist name]" when an artist is clicked.

#9 fix missing space in ellipsis limited tag view between artist name and album year.

monkeypox

added a commit
that referenced
this issue

Mar 21, 2020

@monkeypox

#1 - rewrite to show coverview by adding class 'cv' to body instead of js gymnastics.

#2 - added a global var 'cv' that denotes cover view state to avoid a conditional with a jquery selector in the setinterval timer where it's really expensive.

#3 - modified the cv layout a little bit including a new fat thumb for the timeline but I dunno. the album title should prob be in a div below the cover so it can be more naturally placed.

monkeypox

added a commit
that referenced
this issue

Mar 25, 2020

@monkeypox

This is pretty small but...

#1 makes the spinner constant when doing the update library menu item by moving where the global thumb update var is set and then checking if it's set before hiding the busy spinner, it could be done both places if this is needed for configs.

#2 the modal background is currently theme background-ish, it should probably just be dark, not sure tho.

#3 adds back in a check for the current panel being playback for the mobile scroll handler as otherwise it'd show the playlist on mobile in other views.

#4 the *TEST* lines we discussed, it seems like a browser rendring quirk, I used css instead e.g. line #460 & 463 of panels.css handles the coverart-link case

#5 restored the original playbar element order wrt title & switch to fix the "dead zone"

#6 use rem instead of em because bootstrap sets btn font size to 0 for some reason

#7 clear config icon button background color

#8 use 49/51 left-right split for modals, need to dbl-check there's no spillover tho

#9 used smaller playbar play control button padding for mobile portrait

monkeypox

added a commit
that referenced
this issue

Apr 3, 2020

@monkeypox

This does two things.

#1 it stops the knob cycling behavior where moving past the knob volume boundaries (e.g. 0) would give a max value result which could lead to unhappy voume happenings.

#2 it prevents a volume-step-limiter +10 value from repeating, the user is now required to tap the knob, this prevents a runaway volume escalation which could also result in unhappy volume happenings.

This was referenced

May 24, 2020

monkeypox

added a commit
that referenced
this issue

Sep 28, 2020

@monkeypox

The lazyload library was never designed to deal with dynamically added content so we used settimeout statements to pause for the lists to populate. This doesn't always happen in time which results in no thumbs.

This implements .when().then() to the list output routines with the then() being a call to lazyLode(). This lets the list finish populating before lazyload() is ever called. All other subsequent calls to .lazyload() shouldn't need to be placed in a settimeout statement.

This also:

#1 limits the scope of the .limited class some more

#2 fixes a playlist thumb margin issue

#3 hides the e.g. radio search reset by default so it doesn't flash on/off on page reload

#4 adds object-fit as discussed on the forum

#5 adds lazylode calls to the thumb column setting as when it increases more thumbs are exposed, etc.

#6 reverts the conditional in the setinterval to use coverview & currentView

#7 fixes radio search (span div swap)

monkeypox

added a commit
that referenced
this issue

Sep 28, 2020

@monkeypox

The .when().then() pair seemed great and all but it caused the browser to hang sometimes, so back to not messing with the big lists and using a different method for radio & playlist that works but isn't associated with bad juju.

Also

#1 back to old .limited css as otherwise it didn't apply to tag lists, dur.

#2 removed the space that caused git to throw a conflict

#3 removed some timeouts in scripts-panels as lazyLode isn't called directly in ra-refresh anymore.

monkeypox

added a commit
that referenced
this issue

Sep 29, 2020

@monkeypox

It benchmarks quite a bit faster.

Also:

#1 switch back to .limited .lib-entry span and added text overflow stuff to genre & artist li's

#2 moved the initTime calc to top of loop becasue mobile uses it too

#3 cleaned up the alpha blend DOMSubtree code. We should look at switching to MutationObserver one of these days so chrome stops console spamming.

monkeypox

added a commit
that referenced
this issue

Sep 29, 2020

@monkeypox

They weren't covered under the current rule set.

Also:

#1 remove a display:block !important from #albumcovers .album-name that doesn't seem needed

#2 add a rule so the radio search reset is display:none so it doesn't load up as unhidden

#3 make cover menu circle a bit less opaque (.6 -> .5)

monkeypox

added a commit
that referenced
this issue

Oct 2, 2020

@monkeypox

This circumvents an issue where lazyload would sometimes be called before the list had populated by adding a function that uses javascript promises to let moode know when an element exists, i.e. $.ensure(this).then(that).

It also:

#1 checks if the view is active before calling lazylode (looking at you playlist & radio)

#2 checks to see if lazyload has already been called and if so skips the actual lazyload call.

#3 allows a call to force lazyload to run anyway (e.g. for typedown search)

#4 allows setting skip_invisible (e.g. for typedown search)

#5 switch radio & playlist to use innerHTML like the two library lists

#6 adds an id to the play queue list markup to facilitate #5

#6 fixes a bug in renderui with the default cover image (was missing a '" ' at the end of the src.

#7 limits MPD.json['date'] to 4 characters which should maybe be done in the php but whatever

#8 adjusts the mobile playbar title text a little: slighty larger, shifted to the left a little.

#9 remove placeholder graphic from lazyload library, sets skip_invisible back to original default value of false and comments out srcset stuff we don't use.

monkeypox

added a commit
that referenced
this issue

Oct 3, 2020

@monkeypox

This removes a lot of now unneeded settimeout code blocks and moves the customscroll and active element lines to lazylode.

Also:

#1 makes the album title on album view font-weight 600

#2 we should remove the loading library popup as loading the library is fast enough now not to need it

monkeypox

added a commit
that referenced
this issue

Oct 4, 2020

@monkeypox

This adds scrolling to and selecting of the album selected by the ralbum button.

Also:

#1 change random-album to be smarter about what li to remove the active class from

#2 fixes second volume number positioning & size for people who love volume numbers

#3 makes the m menu a bigger hit target, this addresses an issue where ios lets you drag the scrollbar and so was annoying for things on the right side of the screen.

#4 moves the random album button (tag/album) to the right side and makes it a bigger hit target

#5 adjusts the ralbum timeout from 1500 to 500.

#6 fixes an issue where show tracks... on mobile in album view would have the album covers overlapping the bottom row region a bit

#7 WIP for a delayed notification popup on long library loads, not very much testing and it auto-dismisses while the library may still be loading but it does that now so...

monkeypox

added a commit
that referenced
this issue

Oct 5, 2020

@monkeypox

#1 remove the large overlay volume knob from being set to 15vw for large displays

#2 minor code simplification in getThumbHW (use var -= value instead of var = var - value)

#3 set UI.mobile on resize event

#4 make knob thickness on the playback screen slightly bigger to work around apparent bug in ios 14 I just noticed (.13 to .14)

monkeypox

added a commit
that referenced
this issue

Oct 10, 2020

@monkeypox

WIP as the appearance section is probably going away but this allows a user to filter matching with mpd 'search any'.

Also:

#1 adds a !f bang command to the library search so you can quickly apply a filter

#2 make setLibMenuHeader() show the current filter after the regular text in parenthesis

#3 added a call to setLibMenuHeader() in scripts-library after it renders the library so filtering gets the right header

#4 makes context menus min-width 12.5rem for spacing niceness

#5 Fixes the library menu (aka viewswitch) to use the normal font, adjusts the spacing to match the m menu and pads the text-only items to match the icon ones.

#6 removed a font size bump to mobile portrait, the text on the screen is alreay larger than the rest of the text on the screen, maybe we need to adjust if the font setting has been bumped?

#7 fixed an error in adaptive backgrounds if it couldn't pull a color

monkeypox

added a commit
that referenced
this issue

Oct 12, 2020

@monkeypox

#1 - use a conditional for setLibMenuHeader() in loadLibrary() so it only applies for album & tag views

#2 - smarter application of (filter)

#3 - move cleartimeout to try to clear up an issue where it was showing up when switching tabs

#4 add a cleartimeout to filterhelp() to double good clear it out

monkeypox

added a commit
that referenced
this issue

Oct 14, 2020

@monkeypox

This adds a menu item the the library menu that will clear the current filter.

Also:

#1 adds the fa-undo icon for use by the clear filter menu item

#2 the menu header text output no longer needs a conditional, duh

#3 filterhelp clears the filter search reset button

#4 comments out one-touch menu item and reshuffles context menu so play is on top, adds a separator before the track info item.

While trying to setup NFS on an OVM 3.2 configuration on OEL 5.9, I followed the documentation to the letter but when time came to start the NFS daemon I kept getting the error above.

[root@ovm /]# service nfs start
Starting NFS services: [ OK ]
Starting NFS quotas: Cannot register service: RPC: Unable to receive; errno = Connection refused
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
[FAILED]
Starting NFS daemon: [FAILED]

After a little googling, it turns out that RPCBind may not be running.

[root@ovm /]# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused

Perhaps I needed to update my NFS Utility packages?

[root@ovm /]# yum install nfs-utils
Loaded plugins: rhnplugin, security
This system is not registered with ULN.
You can use up2date --register to register.
ULN support will be disabled.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package nfs-utils.x86_64 1:1.0.9-70.el5 set to be updated
--> Processing Dependency: initscripts >= 8.45.43 for package: nfs-utils
--> Running transaction check
---> Package initscripts.x86_64 0:8.45.44-3.0.1.el5 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================================================================================================
Package Arch Version Repository Size
=============================================================================================================================================================
Updating:
nfs-utils x86_64 1:1.0.9-70.el5 el5_latest 409 k
Updating for dependencies:
initscripts x86_64 8.45.44-3.0.1.el5 el5_latest 1.6 M

Transaction Summary
=============================================================================================================================================================
Install 0 Package(s)
Upgrade 2 Package(s)

Total download size: 2.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): nfs-utils-1.0.9-70.el5.x86_64.rpm | 409 kB 00:00 
(2/2): initscripts-8.45.44-3.0.1.el5.x86_64.rpm | 1.6 MB 00:01 
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 598 kB/s | 2.0 MB 00:03 
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : initscripts 1/4 
warning: /etc/sysctl.conf created as /etc/sysctl.conf.rpmnew
Updating : nfs-utils 2/4 
Cleanup : nfs-utils 3/4 
Cleanup : initscripts 4/4

Updated:
nfs-utils.x86_64 1:1.0.9-70.el5

Dependency Updated:
initscripts.x86_64 0:8.45.44-3.0.1.el5

Complete!

Then I tried the RPC info command again, but no luck!

[root@ovm /]# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused

Portmap? Oh, that would explain a lot since NFS apparently requires port mapper service to run.

[root@ovm /]# chkconfig portmap on
[root@ovm yum.repos.d]# service portmap start

Try RPC info again. Aha, that did it!

[root@ovm yum.repos.d]# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper

Finally, restart the NFS Service and set it to autostart.

[root@ovm /]# service nfs start
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
[root@ovm /]# chkconfig nfs on

Hope this was helpful!

Cheers!

Понравилась статья? Поделить с друзьями:
  • Rpc error program not registered
  • Rpc error no cluster leader
  • Rpc error my keenetic
  • Rpc error in moveitem rust
  • Rpc error in doplace rust plugin