Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About uberchuckie

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ah, no. You still need to make changes like https://docs.observium.org/device_linux/. I'll take a look when I have time.
  2. I took a quick look and I think I know what happened to your attempt. I am assuming that you did something similar to The Observium docs page isn't loading for me right now. When you copy the files, you have to copy them to the host, not within the container. xinetd needs to be running on the unRAID server itself (which you've already installed with nerdtools). I'll try to get this working on my server when I have time. I don't think there are any changes to the Observium image itself.
  3. Ok, I see what you’re asking for. Do you have a sample MIB you want me to try get working? Sent from my iPhone using Tapatalk
  4. Ok. I’ll take a look when I have a chance. Sent from my iPhone using Tapatalk
  5. This is a product question where I think you'll be better served by their community forum.
  6. Try: Stop the container, delete the observium directory in your appdata directory and start the container again. My guess is that the database initialization didn't run to completion before it was killed. Hard to say without seeing the entire log.
  7. For some reason, the database schema initialization failed. I'll see if I can reproduce it. Stop the container, delete the observium directory in your appdata directory and start the container again. EDIT: I tried to reproduce the problem by starting the docker container with a /config volume mapping pointing to an empty directory. The database initialization worked for me.
  8. I don't think it's possible. I assume you set the IP via the custom br0 network. I see "-e 'TCP_PORT_8668'='80'" in the docker run command line but it doesn't work.
  9. I’ll look at the log this weekend and also see if I can reproduce the problem. Sent from my iPhone using Tapatalk
  10. The container was killed while it was setting up the database. Delete the observium directory, start the container and let the setup script run to its completion. Sent from my iPhone using Tapatalk
  11. This is a new setup? The logs shows there already was a configuration in in the config volume. > Using existing PHP database config file. Try deleting the observium directory in your appdata directory and start the container again. I don't think the database schema or the users were created properly.
  12. I've pushed a new image where Observium's discovery.php script is now ran with the debug flag. If other users have problems with discovery script, I'll have a better idea what went wrong.
  13. I actually saw your first post before you edited it. The last line of the log file shows that the database schema creation did not complete. Either something went wrong or it was still initializing the database. 10 minutes is a really long time. On the first run, it should show something like: What kind of hardware are you running? I think if the container is killed before the database initialization completes, subsequent restarts won't run the first run script again because the database has already been initialized. I think the first run script can be improved to pick up where it left off.
  14. Can you delete your appdata files for observium, restart the container and post the logs? I can't reproduce the problem on my setup.
  15. I just created a test container from scratch. The UI does come up but for the first run, it takes a minute or two to initialize the database. If you tried to logon right away, it won't work, and that's what people are seeing I think. Here is my log file from the test container: