Asigra first time run show error 404

okynnor

Explorer
Joined
Mar 14, 2019
Messages
71
Hi,

I tried Asigra after receiving the email blast introducing it. I thought it was a neat idea.
I installed it successfully (easy). But when first run after pressing on the three dots and selecting "management"

I was showing and Error 404.

I tried with Chrome, Safair and the new Edge (chromium ed.). Each showed the same error..

Would someone know what's going on?

Doesn't seem to be a good impression so far.

Ron
 

Shane-Kelly

Dabbler
Joined
Jun 7, 2019
Messages
10
Hi Ron

Same problem - here - have sent a couple of emails to asigra support. registered for their supportv forum - no joy there.

went thru asigra supplied docs as well. Surely someone @ ixsystems should be able to steer us in the right direction as they r incoprating with truenas
 
D

dlavigne

Guest
Are you using an internal static or DHCP IP address? Static should work, there is an open ticket to add support for DHCP reservations.
 

Shane-Kelly

Dabbler
Joined
Jun 7, 2019
Messages
10
apologies r u referring to jail that asigra is using? - that i let dhcp assign - i will manaully assign ip in jail and retry
 
D

dlavigne

Guest
Let us know. Asigra's licensing server requires a static public IP plus a static internal IP.
 

Shane-Kelly

Dabbler
Joined
Jun 7, 2019
Messages
10
Behind an adsl router with nat - ip address on adsl do change but not since i registered. do i need to setup Dynamic dns on freenas and implement port forwarding to freenas box to get asigra to work?
 
D

dlavigne

Guest
Yeah, sounds like something is blocking it. Anything in the firewall log?
 

Shane-Kelly

Dabbler
Joined
Jun 7, 2019
Messages
10
disabled firewall on adsl router still same problem-do u know if there is a tutorial for asigra freemas plugin ?
 
D

dlavigne

Guest
Just what is in https://www.ixsystems.com/blog/asigra-plugin/. Please create a ticket at bugs.ixsystems.com and report the issue here. We may have to confirm with the Asigra engineers what their software requires on the internal network side as their use case may be more restrictive due to their licensing requirements.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,456
I'm seeing the same problem. Installed the plugin with a static IP, and the post-installation messages say I can reach the management page at http://192.168.1.68/asigra/DSOP.jnlp--when I browse there I get 404 (and yes, the IP is correct). When I click the three-dot menu for the installed plugin and select Management, it takes me to the same URL, with the same result. If I browse to the bare IP address, I see this:
1559958039937.png

The link goes to the same URL, which (once again) gives the same result.

Further investigation reveals that DSOP.jnlp doesn't exist in the jail:
Code:
root@asigra:~ # find / -name DSOP.jnlp
root@asigra:~ # find / -name \*.jnlp
root@asigra:~ # 

In fact, /usr/local/www/asigra appears to be empty:
Code:
root@asigra:~ # cd /usr/local/www/asigra
root@asigra:/usr/local/www/asigra # ls
root@asigra:/usr/local/www/asigra # 
 

jvs

Cadet
Joined
Mar 22, 2017
Messages
1
I see the same problem here too. I noticed after setting up the plugin an error: 'Failed to install the following 1 package(s): /root/dssystem-14.1.txz'. I found out the script which is executed resides here. At line 78 and 79 the system tries to fetch two files.

Code:
fetch http://builds.ixsystems.com/ix-iso/asigra/14.1-20190301/DS-Operator.zip
fetch http://builds.ixsystems.com/ix-iso/asigra/14.1-20190301/dssystem-14.1.txz


The first contains the plugin admin portal, the second is a package. The pkg add command at line 82 cannot find the package and causes the above error message.

I think these two files cannot be fetched because if I try to fetch them manually then I got "no route to host" error message.
 

John E.

Cadet
Joined
Mar 19, 2017
Messages
4
....I got "no route to host" error message.

Same, and shelling into jail (with a static IP assigned), and checking connectivity, shows this
Code:
root@asigra:~ # fetch -v http://builds.ixsystems.com/ix-iso/asigra/14.1-20190301/DS-Operator.zip
resolving server address: builds.ixsystems.com:80
failed to connect to builds.ixsystems.com:80
fetch: http://builds.ixsystems.com/ix-iso/asigra/14.1-20190301/DS-Operator.zip:No route to host

root@asigra:~ # traceroute builds.ixsystems.com
traceroute to builds.ixsystems.com (12.189.233.133), 64 hops max, 40 byte packets
...
3  172.99.47.22 (172.99.47.22)  5.011 ms
    172.99.44.42 (172.99.44.42)  9.028 ms
    172.99.44.44 (172.99.44.44)  6.646 ms
4  ae7---0.scr01.mias.fl.frontiernet.net (74.40.3.69)  11.779 ms  11.265 ms
    ae8---0.scr02.mias.fl.frontiernet.net (74.40.3.73)  14.875 ms
5  ae1---0.cbr02.mias.fl.frontiernet.net (74.40.1.130)  14.187 ms  14.127 ms  15.023 ms
6  12.245.110.17 (12.245.110.17)  14.941 ms  14.257 ms  14.991 ms
7  fldfl81crs.ip.att.net (12.122.155.162)  42.447 ms  41.702 ms  39.963 ms
8  cr2.ormfl.ip.att.net (12.123.6.50)  39.944 ms  36.420 ms  32.442 ms
9  attga21crs.ip.att.net (12.122.28.197)  34.946 ms  34.113 ms  35.013 ms
10  nsvtn22crs.ip.att.net (12.122.2.6)  34.968 ms  39.337 ms  37.407 ms
11  12.123.129.29 (12.123.129.29)  32.355 ms  31.396 ms  32.531 ms
12  12.88.186.54 (12.88.186.54)  42.394 ms  41.548 ms  42.473 ms
13  12.88.186.54 (12.88.186.54)  309.987 ms !H  3039.157 ms !H  3037.701 ms !H

So, it looks like the jail resolves DNS, and has IP connectivity to the Internet, but maybe something downstream [between 12.88.186.54 and builds.ixsystems.com (12.189.233.133)] is getting hung up.
 

Kevlaar

Cadet
Joined
May 10, 2017
Messages
7
So, it looks like the jail resolves DNS, and has IP connectivity to the Internet, but maybe something downstream [between 12.88.186.54 and builds.ixsystems.com (12.189.233.133)] is getting hung up.
I am getting the same - the traceroute ends at 12.88.186.54
 

Naelr

Cadet
Joined
Jan 6, 2015
Messages
4
I have received the exact same error on two different installs. 'Failed to install the following 1 package(s): /root/dssystem-14.1.txz', Watching this thread for any update this is the only one I have found with the same error. Why would IXsystems push what looks to be an amazing addition so hard with this error? I have 2 use cases right now I can think this would be awesome for clients I have and they both have freenas certified equipment. Not to mention here at home. Please someone from IX look into this quickly.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,456

John E.

Cadet
Joined
Mar 19, 2017
Messages
4
Why would IXsystems push what looks to be an amazing addition so hard with this error? ....Please someone from IX look into this quickly.
It looks like it's a Internet routing problem somewhere upstream from them. As such, it may even work fine from some network paths, but not other network paths. Hopefully, they realize this and not just check out the "bug" from only one (working) source address and consider it "not replicatable".
 

Naelr

Cadet
Joined
Jan 6, 2015
Messages
4
I didn't see a bug filed on this, so I created one here: https://jira.ixsystems.com/browse/NAS-102054

Complaining on the forum doesn't typically get the devs' attention.
You are so very correct sir.. I should have just filed a bug rather then complain... I will try to do the correct thing next time..
Thank you very much for taking it upon yourself to fix my mistake. I would appear that it does now work as did as was suggested in that bug and it installed correctly. testing it out now...
 
Top