-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
Just tried to install a new server after a restart I have attached a screenshot showing the error & that it has infact made the folder... this has me mind boggled.
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
I'm using unraid 6.9.2 probably time to update but don't want to break any of the other dockers which are working by updating. My unraid mounts on the docker config page are: 0.0.0.0:8080/TCP0.0.0.0:8085 /etc/pterodactyl -> /mnt/user/pterodactyl-node/Etc/ /var/run/docker.sock -> /var/run/docker.sock /mnt/user/pterodactyl-node/data -> /mnt/user/pterodactyl-node/Data/ /tmp/pterodactyl -> /tmp/pterodactyl My config.yml file paths are root_directory: /mnt/user/pterodactyl-node/data log_directory: /var/log/pterodactyl data: /mnt/user/pterodactyl-node/data archive_directory: /mnt/user/pterodactyl-node/data/archives backup_directory: /mnt/user/pterodactyl-node/data/backups tmp_directory: /tmp/pterodactyl username: pterodactyl timezone: Europe/London I added the additional /mnt/user/pterodactyl-node/data to unraid in an attempt to get rid of the error by adding the exact path it was asking for but this has not made any difference. I know this is almost certainly some little oversight on my part but I cannot see it anywhere. Thanks for any suggestions.
-
Pterodactyl Panel Install & Configure on Unraid using DOCKER (2021)
Is anyone able to help with this error I am getting from the pterodactyl Daemon. ERROR: [Jun 12 09:49:05.975] failed to complete server re-install process error=Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /mnt/user/pterodactyl-node/data/94163d68-1be6-422a-93be-605aee16c962 server=94163d68-1be6-422a-93be-605aee16c962 Stacktrace: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /mnt/user/pterodactyl-node/data/94163d68-1be6-422a-93be-605aee16c962 The folder and location it is referring to do exist and it does have access as it actually created the 94163d68-1be6-422a-93be-605aee16c962 folder right before spitting out the error, this happens with any server I try to setup using both the Ibracorp docker template and the official one. Thanks in advanced for any suggestions.
-
Ultimate UNRAID Dashboard (UUD)
I did I have tried both versions of the psot argument I have installed telegraf alpine, if I use the non alpine post arguments then telegraf will not boot atall and using the alpine post arguments I get everything bar ipmi working.
-
Ultimate UNRAID Dashboard (UUD)
Hi guys, anyone know what could be causing this error: Error: Unable to establish IPMI v1.5 / RMCP session 2021-01-17T20:24:10Z E! [inputs.ipmi_sensor] Error in plugin: failed to run command /usr/sbin/ipmitool -H 192.168.0.131 -U telegraf -P telegraf -I lan sdr: exit status 1 - Error: Unable to establish LAN session This is trying to connect to my Dell R710s IDRAC express using a new read only account iv created. I have used the additional argument in telegrafs configuration that's supposed to download ipmi tools but my guess is it hasn't downloaded? Is there a easy way for me to test this / manually install ipmi tools? Still finding my feet when it comes to Linux based systems so my apologies if this is a obvious problem that iv failed to spot. Thanks in advanced for any help. Edit I'm on the most recent stable build of unraid and I have enabled my Idrac access over lan and can open a connection to it using the login iv given to telegraf in my browser. Here is my telegraf conf section regarding ipmi I have changed username and password for obvious reasons everything else is identical. GNU nano 4.6 telegraf.conf # # Read metrics from the bare metal servers via IPMI [[inputs.ipmi_sensor]] # ## optionally specify the path to the ipmitool executable # # path = "/usr/bin/ipmitool" # ## # ## Setting 'use_sudo' to true will make use of sudo to run ipmitool. # ## Sudo must be configured to allow the telegraf user to run ipmitool # ## without a password. # ## use_sudo = true # ## # ## optionally force session privilege level. Can be CALLBACK, USER, OPER># # privilege = "ADMINISTRATOR" # ## # ## optionally specify one or more servers via a url matching # ## [username[:password]@][lan[(ip)]] # ## e.g. # ## root:passwd@lan(127.0.0.1) # ## # ## if no servers are specified, local machine sensor stats will be queri># ## servers = ["username:password@lan(192.168.0.131)"] # # ## Recommended: use metric 'interval' that is a multiple of 'timeout' to># ## gaps or overlap in pulled data interval = "30s" # # #
Joe L
Members
-
Joined
-
Last visited