Jump to content

Higgins12

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Higgins12

  • Rank
    Newbie
  1. Great. That worked. Removed the default Gateway from the 10Gbit interface and all back to normal
  2. Still having the same Problem which I had with RC6. After updating the Server is unable to communicate with the outer world. There are 3 NIC Interfaces. 2 Build-in and 1 10Gbit card direct connection to the PC. Strangely the Server now tries to route all traffic thru the 10Gbit interface. If I deactivate and restart the Interface all is well, after rebooting the Server I'm back at the start. This is with the 10GBit Interface active: and here when I have restarted the Interface: tried to completely remove and reconfigure the 10GBit interface, no change
  3. I'm having the exact same issue. After updating to RC6 the Server is unable to communicate with the outer world. Reverted back to RC5 all good again.
  4. Ok thanks. Updated to 6.5.5 will see what it does tonight wehen the next cron should run. Edit: Well great, that worked. All Jobs running again. Thanks
  5. I'm a bit lost here. I installed the plugin and configured it. Well but it just does nothing. In fact now not a single cronjob does work anymore. Neither the mover which I set to 12am kicks in and either Fix Common Problems doesn't do any scans anymore. crontab -l only lists # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null but the file /etc/cron.d/root has everything in it # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 0 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated Unraid OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated cron settings for docker autoupdates 30 23 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1 # Generated cron settings for plugin autoupdates 0 23 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # Generated ssd trim schedule: 0 23 * * * /sbin/fstrim -a -v | logger &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null tried to uninstall the plugin but still the same. Not a single cronjob is running. Looked thru the log files and can't even find a single instance for crontab. What am I doing wrong here?