Hi,
Since the update 1.5.1012, we are unable to add Qnap server to Q'center.
We use address type qcenter.domain.com port 8080 and registration code.
Port 8080 is open and forwarded to the Q'center.
We have actualy 38 NAS connected but can't add another.
The error is : Q'center Agent : Failed to add..
Version of Qnap : 4.3.3 (Can't connect with 4.2.3 also)
Thank's in advance.
Sol-Info
Unable to add serveur to Q'center 1.5.1012
-
- New here
- Posts: 9
- Joined: Mon Sep 12, 2016 2:39 pm
-
- New here
- Posts: 2
- Joined: Tue May 09, 2017 7:58 pm
Re: Unable to add serveur to Q'center 1.5.1012
Hello,
Not that it is any help, but I am having exactly the same isssue with 2 NAS out of my fleet. I have about 20 added to Q'Center, Most of them the exact same model as the two with the issue.
My QCenter itself is running on ESX 6.0
QCenter version is: 1.3.519
Model of QNAP having the issue: TS-453A
The issue occurs when using the connector being used between the QNAP and a NAT router. QNAP assistant. There are no VLANs. Straight shot out from the firewall to the Q’Center. The bulk of the QNAPs I have connected are working perfectly in this scenario.
You can successfully authenticate and connect using the connector. The issue occurs when the agent is installed. The form is auto-filled by the connector, the wheel starts whirling, it says 'failed to add' and Q'Center logs an event in the Q'Center
event log.
Event says: Server '192.168.1.15' failed to add to Q'Center. The IP is a generalization, it is always the local IP of the QNAP that failed to add.
Thanks for any information, even if it is just that we have to wait for a patch.
EDIT: Doesn't hurt to say that I've tried extreme measures to verify it isn't being blocked locally, even going so far as to temporarily assign an IP to the Q'Center, put it in a DMZ, then do the same for the QNAP with the problem.
Not that it is any help, but I am having exactly the same isssue with 2 NAS out of my fleet. I have about 20 added to Q'Center, Most of them the exact same model as the two with the issue.
My QCenter itself is running on ESX 6.0
QCenter version is: 1.3.519
Model of QNAP having the issue: TS-453A
The issue occurs when using the connector being used between the QNAP and a NAT router. QNAP assistant. There are no VLANs. Straight shot out from the firewall to the Q’Center. The bulk of the QNAPs I have connected are working perfectly in this scenario.
You can successfully authenticate and connect using the connector. The issue occurs when the agent is installed. The form is auto-filled by the connector, the wheel starts whirling, it says 'failed to add' and Q'Center logs an event in the Q'Center
event log.
Event says: Server '192.168.1.15' failed to add to Q'Center. The IP is a generalization, it is always the local IP of the QNAP that failed to add.
Thanks for any information, even if it is just that we have to wait for a patch.
EDIT: Doesn't hurt to say that I've tried extreme measures to verify it isn't being blocked locally, even going so far as to temporarily assign an IP to the Q'Center, put it in a DMZ, then do the same for the QNAP with the problem.
-
- Starting out
- Posts: 35
- Joined: Fri Feb 12, 2010 8:57 pm
Re: Unable to add serveur to Q'center 1.5.1012
Hi
I see the same issue.
I'm trying to setup Qcenter, and all models are on 4.3.3. - with Qcenter 1.5.1012
The only one I can add is the local QNAP (where the Qcenter is running)
The 2 others are on other network, and I have followed the process, but they all end up stating that they can't add.
One thin I have noticed, is after trying this. If I go into the Qcenter console and try to manually add a device, it throws an error that the subsystem isn't responding.
The only way to solve this is to stop Qcenter, and start it again
Do you also see this behaviour?
- Henning
I see the same issue.
I'm trying to setup Qcenter, and all models are on 4.3.3. - with Qcenter 1.5.1012
The only one I can add is the local QNAP (where the Qcenter is running)
The 2 others are on other network, and I have followed the process, but they all end up stating that they can't add.
One thin I have noticed, is after trying this. If I go into the Qcenter console and try to manually add a device, it throws an error that the subsystem isn't responding.
The only way to solve this is to stop Qcenter, and start it again
Do you also see this behaviour?
- Henning
-
- First post
- Posts: 1
- Joined: Mon May 15, 2017 8:34 pm
Re: Unable to add serveur to Q'center 1.5.1012
Same issue here,
Q'center virtual appliance version: 1.3.519
QNAP TVS-682 firmware: 4.3.3
What I do see in the logs is that adding the server fails when it tries to update the agent on the client from 1.2.101 to 1.3.519
Q'center virtual appliance version: 1.3.519
QNAP TVS-682 firmware: 4.3.3
What I do see in the logs is that adding the server fails when it tries to update the agent on the client from 1.2.101 to 1.3.519
You do not have the required permissions to view the files attached to this post.
-
- First post
- Posts: 1
- Joined: Wed May 17, 2017 7:46 pm
Re: Unable to add serveur to Q'center 1.5.1012
Same Issue!
reported Dump to Qnap and wait for theyr answer.
We believe that Fresh new installed Qnap with 4.3.3 are involved with this problem: Q'Agent will not connect : local or remote. It reaches the server bu something hangs...
we also found this error in logs: in ganglia log file "udp apr_pollset_poll returned unexpected status 22 = Invalid argument" no documentation found
Besides, a 4.3.3 Qcenter server accepts 4.3.2 Qcenter Agents: local or remote.
Best Rgrds
Eric
Paris
France
reported Dump to Qnap and wait for theyr answer.
We believe that Fresh new installed Qnap with 4.3.3 are involved with this problem: Q'Agent will not connect : local or remote. It reaches the server bu something hangs...
we also found this error in logs: in ganglia log file "udp apr_pollset_poll returned unexpected status 22 = Invalid argument" no documentation found
Besides, a 4.3.3 Qcenter server accepts 4.3.2 Qcenter Agents: local or remote.
Best Rgrds
Eric
Paris
France
-
- New here
- Posts: 9
- Joined: Mon Sep 12, 2016 2:39 pm
Re: Unable to add serveur to Q'center 1.5.1012
No change with the update 4.3.3.0188..
-
- New here
- Posts: 2
- Joined: Tue May 09, 2017 7:58 pm
Re: Unable to add serveur to Q'center 1.5.1012
Came here to say the same. Updated a QNAP that came with 4.3.3 to the new 4.3.3 release and still seeing the same problem.
-
- New here
- Posts: 9
- Joined: Mon Sep 12, 2016 2:39 pm
Re: Unable to add serveur to Q'center 1.5.1012
It's now working with the new update (1.5.1025).
-
- New here
- Posts: 4
- Joined: Tue Oct 27, 2020 5:17 pm
Re: Unable to add serveur to Q'center 1.5.1012
I've the same issue with 4.5.1.1465 build 20201024 and only one device out of 7. Frustrating.
-
- Know my way around
- Posts: 120
- Joined: Sun Mar 20, 2011 4:34 am
- Location: Upper Youghiogheny, MD
Re: Unable to add serveur to Q'center 1.5.1012
It may have been an issue on 4.5.1.1465 but I didn't notice it until 4.5.1.1480. On 4.5.1.1480 on TS-EC1280U-RP it's q'Center stopped showing SOME info (disk/storage/firmware vers). I then upgraded a TS-EC2480U-RP that was showing fine in Q'Center when on 4.4.3 but on 4.5.1.1480 now missing same info like with the 1280U. All other units showed fine in Q'Center including a TS-853 Pro that is on 4.5.1, but I had one unit never added to q'Center, a TS-873U-RP on 4.5.1.1480, so I went to add it to see if it had missing info issue; It would not add it to Q'Center! Upgraded the three problem units from 4.5.1.1480 to 4.5.1.1495. Problem remains unchanged.
I then moved Q'Center from a TS-EC1679U-RP to the TS-873U-RP that I had not been able to add to Q'Center. The Q'Center version updated with the move from 1.10.1003 to 1.10.6000 (20200813), and I COULD add the TS-873U-RP to Q'Center, but it has same issues there as the two EC-xx80U units.
I opened ticket Q-202011-57967 with helpdesk 26 November but they have not responded yet.
TS-EC2480U-RP@TS-X80U_20230718-4.5.4.2467 16GB RAM; QM2-2P10G1TA 2 x 2TB R1; QM2-2P-384 2 x 2TB R0c; 24 x 6TB
TS-EC1679U-RP@TS-1679U_20220526-4.3.6.2050 32GB RAM; QM2-2P10G1T 2 x 1TB R1; QM2-2P-344 2 x 2TB R0c; 14 x 8TB
TS-EC1280U-RP@TS-X80U_20231128-5.1.4.2596 32GB RAM; QM2-2P10G1TA 2 x 2TB R1; QM2-2P-344 2 x 2TB R0c; 12 x 10TB
TVS-1271U-RP@TVS-X71U_20231110-5.1.3.2578 32GB RAM; QM2-2P10G1T 2 x .5TB R1; QM2-2P-344 2 x 2TB R1c; 12 x 8TB
TS-873U-RP@TS-X73U_20231128-5.1.4.2596 24GB RAM; 2 x 1TB WD SSD R1; QM2-2P10G1TA 2 x 2TB R0c; 8 x 14TB
TS-873A@TS-X73A_20230421-h5.0.1.2376 64GB RAM; 2 x 2TB WD SSD R1; QM2-2P10G1TA 2 x 1TB R0c; QM2-2P-344 2 x 2TB R1zilslog; 8 x 18TB
TVS-873e@TVS-X73_20230609-5.0.1.2425 64GB RAM; 2 x 2TB WD SSD R1; QM2-2P10G1TA 2 x 2TB R0c; 8 x 14TB
TS-1279U-RP, TS-453U-RP
TS-EC1679U-RP@TS-1679U_20220526-4.3.6.2050 32GB RAM; QM2-2P10G1T 2 x 1TB R1; QM2-2P-344 2 x 2TB R0c; 14 x 8TB
TS-EC1280U-RP@TS-X80U_20231128-5.1.4.2596 32GB RAM; QM2-2P10G1TA 2 x 2TB R1; QM2-2P-344 2 x 2TB R0c; 12 x 10TB
TVS-1271U-RP@TVS-X71U_20231110-5.1.3.2578 32GB RAM; QM2-2P10G1T 2 x .5TB R1; QM2-2P-344 2 x 2TB R1c; 12 x 8TB
TS-873U-RP@TS-X73U_20231128-5.1.4.2596 24GB RAM; 2 x 1TB WD SSD R1; QM2-2P10G1TA 2 x 2TB R0c; 8 x 14TB
TS-873A@TS-X73A_20230421-h5.0.1.2376 64GB RAM; 2 x 2TB WD SSD R1; QM2-2P10G1TA 2 x 1TB R0c; QM2-2P-344 2 x 2TB R1zilslog; 8 x 18TB
TVS-873e@TVS-X73_20230609-5.0.1.2425 64GB RAM; 2 x 2TB WD SSD R1; QM2-2P10G1TA 2 x 2TB R0c; 8 x 14TB
TS-1279U-RP, TS-453U-RP