We’ve been having problems with the router here and not sure what the root cause is just yet. Right now things seem to be working but it’s been flaky last few days. Sorry for the trouble, but I am looking into it and may even end up replacing the router with something solid. May be pfsense? Any recommendations?
The lack of build tools available for pfsense would worry me at least.
Maybe OPNSense (still FreeBSD based), where one can at least build from scratch. At least this was my understanding of the differences.
Any other suggestions anyone? I used to use ipcop, smoothwall etc but now only really need OpenWRT which probably doesn’t cut it for this deployment. Used pfsense for quite some time though before that but like what little hardware I can get away with (low power wise) on the linux OpenWRT front.
OPNsense have some nice Architecture docs: https://docs.opnsense.org/development/architecture.html
I liked that pfsense was based on nanobsd (if I remember correctly) as there was then a redundant system and upgrades went to the non live side, not sure about OPNsense in this sense though.
I’m not router specialists, but just following a simple logic here: if there is a lot of access to the server sitting behind firewall, then NAT table will get hot = lot of ram, fast cpu would be benefiting.
This makes all ARM based solutions crossed off. One could go for ASIC router - those are damn expensive (but good) from cisco and likes … maybe just using a old HP proliant (gen6 is now dirt cheap, I just buy those for nothing [sub 100$] )
firewall software wise, just go with one that has most users using it - more eyes watching for bugs is better (in world of security)
1 Like
Just something to consider:
73GB of ram should reeeeaaaalllllyyyy get stuff going, just put 2 Ethernet cards (less than 10$ or even some kicking about), a 64gb sandisk SSD (30$) and the router of routers is ready to rock and rockstor 
FYI, any news when stuff will be back online / alternative source ? I’ve got 2 fresh install servers that need to be updated … so samba at least works ok.
( I could fire up “yum update” in cron loop for next few days, but I don’t want to knock in your doors to hard guys )
In the mean time, just to keep yum from taking such a long time to timeout, I recommend adding these lines to /etc/yum.repos.d/Rockstor-Testing.repo:
skip_if_unavailable = 1
retries=1Editing the repo file only works if you then yum update via the cmdline, if you go back into the UI it’ll overwrite the file.
Annoyingly, I just did a fresh install, first time, selected testing channel, and now cannot move further
due to the error.
@Glock24 Apologies as I neglected the customary welcome to the Rockstor community.
As for the recent issues re updates it at least has now started working for me (UK).
@Flyer, @Tomasz_Kusmierz, @ghensley, and @niavasha can you also confirm any successful updates, ie a return to normality on this one?
All looks to be OK again from my location at least.
1 Like
i’m more a fan of IPFire, which is GNU/Linux based (might be Gentoo or LFS) and as powerfull as PFSense at least. NIce GUI, many additional packages and a nice community…like u guys
1 Like
All working here!
Thanks!
1 Like
UK:
main update is ok (the one that you “clock on”), but running “yum update” sometimes goes into infinite loop trying to skip a test repo (that is in the subject)
@Tomasz_Kusmierz Thanks. Not really sure what that is about I’m afraid. Is this with your Rockstor configured for testing channel updates and have you made any other yum config changes other than the Web-UI channel selection?
Cheers.
Vanila as much as possible Phil, due to bad experience I tend to no variate from main stream.
@Tomasz_Kusmierz, if yum can’t connect to a repo, it normally retries 10 times, with a 30-second timeout, so it should eventually give up after about 5 minutes. If it’s still failing for you, I recommend erasing yum’s cache and refreshing the repo list:
yum clean all && yum update
Beyond that, I would guess it’s a problem either with your network setup or your internet service provider.
2 Likes
Cheers, I’m coming more from debian angle so no stranger to apt-get … learning yum was not on my priority list. anyway cleaning cache did help (still even thou yum was slightly defunct the rockstor python updates were working ok 
bizzare but hey)
Perhaps that’s due to the disjoint way Rockstor uses yum (like many automated update solutions). The actual update of the caches is handled by yum-cron, which is run hourly and daily. Although I haven’t looked at the Rockstor source which handles the updates, I would guess that it runs “yum -C check-update” to check for updates and “yum -C update” to install them. That -C forces yum to run from the local caches, without querying any repos, so no hang-up on failed remotes.
To bring this topic up again.
I’m running into this problem again. Internet access is fine. Did a “yum clean all && yum update”, but all i get is
[root@rockstor-nas ~]# yum clean all && yum update
Geladene Plugins: changelog, fastestmirror
Quellen werden aufgeräumt:Rockstor-Testing base elrepo epel extras rockstor updates
Cleaning up everything
Cleaning up list of fastest mirrors
Geladene Plugins: changelog, fastestmirror
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30822 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30819 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30816 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30821 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30818 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30818 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30819 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30817 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30823 milliseconds’)
Anderer Spiegelserver wird versucht.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30812 milliseconds’)
Anderer Spiegelserver wird versucht.
One of the configured repositories failed (Subscription channel for testing updates),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled yum --disablerepo=Rockstor-Testing ...
4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage:
yum-config-manager --disable Rockstor-Testing or subscription-manager repos --disable=Rockstor-Testing
5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise:
yum-config-manager --save --setopt=Rockstor-Testing.skip_if_unavailable=true
failure: repodata/repomd.xml from Rockstor-Testing: [Errno 256] No more mirrors to try.
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30822 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30819 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30816 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30821 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30818 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30818 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30819 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30817 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30823 milliseconds’)
http://rockstor.com/rockrepo-testing/repodata/repomd.xml: [Errno 12] Timeout on http://updates.rockstor.com:8999/rockstor-testing/repodata/repomd.xml: (28, ‘Connection timed out after 30812 milliseconds’)
[root@rockstor-nas ~]#