Amahi Forums

After 4months i started my amahi server again, to update en play and practice with it, buth i'm trying to update only every time with almost every server i get the message pycurl error 6 in webmin.

Amahi is all ready trying to update for 2days, and i find this a little bit to long :-S

What is wrong and what must i change in order to have it working proberbly?
Please do it in noob language

Hello,

Usually when you get that error there is some connectivity issue.

Try to update doing this:

a. Open a terminal window.
b. su - and enter your root password.
c. yum update.

This will find all updates and ask you if you want to install them. If this yields the same error, then we definitely have a connectivity issue.

i done a total new install of f12 with amahi

I think there's defently a network issue, because opening a site in the browser isnt working and in the amahi desktop taking a look at application isnt working neither.

doing the yum update, gives me after a while a whole lot of applications wich have to be updated, but at the end again the error 6 :S

For the information my network schematics:

internet ---- Livebox ---- Sitecom router DHCP (192.168.0.1) --->

From my router, cabled and wifi:
|
|----- 192.168.0.100 Main-PC
|----- 192.168.0.101 Amahi PC
|----- etc

Gateway: 192.168.0.1
DNS: 192.168.0.101
192.168.1.1
0.0.0.0

What is going wrong and what do i have to change in order to have everything working, like:
Router as DHCP
Amahi as first dns and when its turned off the isp dns


Also calling pages on the amahi server takes a couple of seconds...

Hello,

You can only have one DNS running. What is happening is sometimes it resolves to your Amahi DNS server and sometimes it resolves to the other. It is random, so you cannot predict.

If your router does not need the dns specified, I would leave it blank. I have had this same issue before and that was the only way to resolve it.

Recommend you make the DNS only the HDA for your clients. May need to refresh your clients dhcp lease. Try that and see what happens.

oh why is it than that you always can give in dns 1 and 2 etc..

And if i change it to 1 dns and i turn off the amahi server will the rest work normaly than?
Isn't there a way you can direkt the url's from the amahi to the amahi and the rest to the normal isp dns?

strange thing is that i installed Fedora12 again, with the update rep etc on, it updated itself.
Everything worked, but after i pressed the install amahi button and it installed itself, i lost my inet connection but i can connect to amahi on my own network????

Hello,

Your loss of connection after install could be another issue. There was some info here in the forums about the same problem, but can't recall where. Also, consider looking in the wiki (http://wiki.amahi.org. There is a network troubleshooter there that might help.

Inderdaad de netwerk troubleshoot zegt dat de dns niet goed werkt, dit is de uitkomst:

Step 4: Your HDA DNS server is NOT working fine for local hostnames.

login: root
Password:
Last login: Thu Sep 9 19:55:31 2010 from h100.markv.com
[root@LHS ~]# nslookup hda
Server: 192.168.0.101
Address: 192.168.0.101#53

Name: hda.MarkV.com
Address: 192.168.0.101

[root@LHS ~]# cat /etc/resolv.conf
nameserver 192.168.0.101
nameserver 192.168.1.1
domain MarkV.com
[root@LHS ~]# ifconfig | grep -A 5 eth0 | grep inet
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::203:47ff:fecc:7663/64 Scope:Link
[root@LHS ~]# service named status
version: 9.6.2-P2-RedHat-9.6.2-5.P2.fc12
CPUs found: 1
worker threads: 1
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 4405) is gestart...
};
};
key "ddnskey" {
algorithm hmac-md5;
secret "8zaPJsiw9tOh2JFv4xiArw==";
};

zone "MarkV.com" IN {
type master;
notify no;
file "dynamic/hda-n2a.conf";
allow-update { key ddnskey; };
check-names ignore;
};

zone "0.168.192.in-addr.arpa" IN {
type master;
notify no;
file "dynamic/hda-a2n.conf";
allow-update { key ddnskey; };
check-names ignore;
};

server 192.168.1.1 {
};
[root@LHS ~]# netstat -an | grep :53
tcp 0 0 192.168.0.101:53 0.0.0.0:* LIST
EN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LIST
EN
tcp 0 0 ::1:53 :::* LIST
EN
udp 0 0 0.0.0.0:5353 0.0.0.0:*

udp 0 0 192.168.0.101:53 0.0.0.0:*

udp 0 0 127.0.0.1:53 0.0.0.0:*

udp 0 0 ::1:53 :::*
h247 A 192.168.0.247
h248 A 192.168.0.248
h249 A 192.168.0.249
h250 A 192.168.0.250
h251 A 192.168.0.251
h252 A 192.168.0.252
h253 A 192.168.0.253
h254 A 192.168.0.254
hda A 192.168.0.101
help A 192.168.0.101
$TTL 7200 ; 2 hours
iPhone A 192.168.0.103
TXT "3111af441c8fce1aa62c489cedc40b908f"
iPod A 192.168.0.106
TXT "31af76255a5341aaa7804e24c9985f327e"
$TTL 86400 ; 1 day
ldap A 192.168.0.101
router A 192.168.0.1
search A 192.168.0.101
setup A 192.168.0.101
webmin A 192.168.0.101
$TTL 7200 ; 2 hours
Wii A 192.168.0.112
TXT "314ca4d458f475ad6ebb5ccb5e0c092b1f"
$TTL 86400 ; 1 day
wiki A 192.168.0.101
76 PTR h076.MarkV.com.
77 PTR h077.MarkV.com.
78 PTR h078.MarkV.com.
79 PTR h079.MarkV.com.
8 PTR h008.MarkV.com.
80 PTR h080.MarkV.com.
81 PTR h081.MarkV.com.
82 PTR h082.MarkV.com.
83 PTR h083.MarkV.com.
84 PTR h084.MarkV.com.
85 PTR h085.MarkV.com.
86 PTR h086.MarkV.com.
87 PTR h087.MarkV.com.
88 PTR h088.MarkV.com.
89 PTR h089.MarkV.com.
9 PTR h009.MarkV.com.
90 PTR h090.MarkV.com.
91 PTR h091.MarkV.com.
92 PTR h092.MarkV.com.
93 PTR h093.MarkV.com.
94 PTR h094.MarkV.com.
95 PTR h095.MarkV.com.
96 PTR h096.MarkV.com.
97 PTR h097.MarkV.com.
98 PTR h098.MarkV.com.
99 PTR h099.MarkV.com.
[root@LHS ~]#

Ik ben wat dit betreft een zware noob haha, dus hopelijk kan iemand mij vertellen aan de hand van dit wat te doen...

Ik dacht altijd, dat hij eerst naar de eerste dns kijkt en komt ie er neit uit dat hij dan naar de 2e kijkt enzo door...