Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: sqlerror on February 04, 2004, 08:29:01 AM
-
Hi,
Using SME 6.0 in server and gateway mode I ran into trouble when deleting a previous added local network.
When removing a previous added local network in the server-manager, an errormessage is displayed telling me an error has occurred when removing local network.
In the server-manager the removed local network disappered from the list of local networks but the local network still occurs in in /etc/hosts.allow, /etc/proftpd.conf and /etc/sysconfig/static-routes
When adding the local network that I previously tried to remopve, the next error is displayed:
network (derived from network and subnet mask ) has already been added. Did not add new network
What would be the command to manually remove a local network?
Jan 30 22:40:38 joenix e-smith[28165]: S90LPRng-restart=action|Event|network-create|Action|S90LPRng-restart|Start|1075498837 848669|End|1075498838 597219|Elapsed|0.74855|Status|65280
Jan 30 22:42:42 joenix e-smith[28539]: S90LPRng-restart=action|Event|network-delete|Action|S90LPRng-restart|Start|1075498961 802322|End|1075498962 585691|Elapsed|0.783369|Status|65280
Jan 30 22:55:47 joenix kernel: hdc: task_no_data_intr: error=0x04 { DriveStatusError }
Jan 31 01:53:06 joenix e-smith[16829]: S90LPRng-restart=action|Event|network-delete|Action|S90LPRng-restart|Start|1075510385 263749|End|1075510386 31687|Elapsed|0.767938|Status|65280
Jan 31 02:03:44 joenix kernel: hdc: task_no_data_intr: error=0x04 { DriveStatusError }
Makes me wonder what the kernel has to say....
I got no clue, maybe this log snippet might give you one...
Thnx,
Geert
-
From the console, go here, /etc/e-smith/events/actions
and pico -w LPRng-restart
change this line
my $status = $lpd->get('status') || "disabled";
to
my $status = $lpd->prop('status') || "disabled";
This is a post Charlie Brady made to devinfo to fix this bug. This is better than the fix I posted to the bugs forum.
-
From the console, go here, /etc/e-smith/events/actions
and pico -w LPRng-restart
...
my $status = $lpd->prop('status') || "disabled";
...
Mrj,
This does fix the problem! Thanks four your solution.
Still the networks added and deleted before I applied Charlie's patch still give me problems. They do not show up in the server-manager but re-adding them is not possible. Somewhere the information on these networks or part of that information is still in the configuration somewhere. Any clues on removing them from the command-line in the console ?
Cheers,
Geert
-
Sorry I couldn't help. I just saw the output with the LPRng stuff and figured I'd give that a shot. I'll have to set up a test box to test this as well.
-
sqlerror,
You should open a bug report. I can duplicate this on box of my test boxes.
-
I have the exact same problem. I deleted the entrys in those 3 files but still no luck trieng to add the local network. Any clue in wich files I can find more entries to delete?
-
Hmm...It might not be correct completly. When you manualy delete the entries in those files the reappear when you add and delete a new local network in the server-manager.
-
What files are you manually deleting. Anyone open a bug report for this yet?
-
Still the networks added and deleted before I applied Charlie's patch still give me problems. They do not show up in the server-manager but re-adding them is not possible. Somewhere the information on these networks or part of that information is still in the configuration somewhere. Any clues on removing them from the command-line in the console ?
Cheers,
Geert
If they don't show up in the server-manager, then they're not in the networks db anymore. Where are you still seeing them? Try re-expanding those templates.
Mike
-
Filled in a bug report about this problem
-
> Any clue in wich files I can find more
> entries to delete?
edit the file /home/e-smith/networks
pico -w /home/e-smith/networks
Delete the lines that don't show up in your server-manager local networks panel.
This worked for me, your experience may differ.
-
Still the networks added and deleted before I applied Charlie's patch still give me problems.
...
If they don't show up in the server-manager, then they're not in the networks db anymore.
...
No, they are still there. They're there as "network-deleted" entries. He'll need to do:
/sbin/e-smith/db networks delete 192.168.3.0
for each network. He can see what the networks are called by doing:
/sbin/e-smith/db networks show
Charlie
-
No, they are still there. They're there as "network-deleted" entries. He'll need to do:
/sbin/e-smith/db networks delete 192.168.3.0
for each network. He can see what the networks are called by doing:
/sbin/e-smith/db networks show
This worked perfectly for me to. I received a nice and quick email from "the bugteam" giving the same solution.
[edit] :-D I thought I quoted a guest....But no I quoted the man that send me the mail form the bugteam. Thanks Charlie [/edit]
-
Hi,
I Thank you all very much for your help with this issue, especially Charlie for his fixes fixed what had to be fixed.
I just succesfully added en deleted the networks that gave me troubles before. I am glad the problem as reported in my original posting is solved.
Cheers,
Sqlerror
No, they are still there. They're there as "network-deleted" entries. He'll need to do:
/sbin/e-smith/db networks delete 192.168.3.0
for each network. He can see what the networks are called by doing:
/sbin/e-smith/db networks show
Charlie
/sbin/e-smith/db networks show:[root@joenix root]# /sbin/e-smith/db networks show
192.168.0.0=network-deleted
Mask=255.255.252.0
Router=192.168.10.1
192.168.10.0=network
Mask=255.255.255.0
SystemLocalNetwork=yes
192.168.100.0=network-deleted
Mask=255.255.252.0
Router=192.168.10.1
[root@joenix root]#
/sbin/e-smith/db networks delete:[root@joenix root]# /sbin/e-smith/db networks delete 192.168.0.0
[root@joenix root]# /sbin/e-smith/db networks delete 192.168.100.0
/sbin/e-smith/db networks show:[root@joenix root]# /sbin/e-smith/db networks show
192.168.10.0=network
Mask=255.255.255.0
SystemLocalNetwork=yes
[root@joenix root]#
Added 192.168.0.0 and 192.168.100.0:Operation status report
Successfully added network 192.168.0.0/255.255.252.0 via router 192.168.10.1.
Operation status report
Successfully added network 192.168.100.0/255.255.252.0 via router 192.168.10.1.
Deleted 192.168.0.0 and 192.168.100.0:Operation status report
Successfully removed network 192.168.0.0/255.255.252.0 via router 192.168.10.1.
Operation status report
Successfully removed network 192.168.100.0/255.255.252.0 via router 192.168.10.1.
/sbin/e-smith/db networks show: [root@joenix root]# /sbin/e-smith/db networks show
192.168.10.0=network
Mask=255.255.255.0
SystemLocalNetwork=yes
[root@joenix root]#
-
Okay, I need serious help here!! I was trying to add my work's static IP to the local networks section so I could limit SSH access to local networks only and still gain access through work. Long story short, I entered the wrong information and submitted before I caught it. Now, I can't get into server-manager at all!
I tried the
/sbin/e-smith/db networks show
command to see the offending network, and then ran:
/sbin/e-smith/db networks delete xxx.xxx.xxx.xxx
as found in this thread and I was successfully able to remove the wrong entry through there.
But now my /etc/httpd/httpd.conf and /etc/httpd/admin-conf/httpd.conf files are riddled with references to this network (IP,) even after removing the network and expanding the template and rebooting the server!
When I issue the
service httpd restart
command, I get:
Stopping httpd: [ FAILED ]
Starting httpd: Syntax error on line 969 of /etc/httpd/conf/httpd.conf:
syntax error in mask portion of network/netmask
[ FAILED ]
Line 969 is the first reference in httpd.conf to the offending network; with 192 references in total.
How in great gravy do I purge this error from my system??? HELP?!? (Not to sound desperate or anything...)
-
Brenno,
you forgot to run
/sbin/e-smith/signal-event remoteaccess-update
This will rebuild all the relevant config files with new DB settings and restart services to activate the change.
-
Brenno,
you forgot to run
/sbin/e-smith/signal-event remoteaccess-update
This will rebuild all the relevant config files with new DB settings and restart services to activate the change.
Boris,
Thanks for the suggestion. Sadly, it didn't work. I can still see the references to the bad network IP in the .conf files :( It did rewrite /etc/httpd/conf/httpd.conf as the file size has shrunk, but /etc/httpd/admin-conf/httpd.conf did not change in size, so it may not have been modified.
However, I don't get the error when I restart the httpd service anymore, so that's promising!
I'm still getting the "502 Proxy Error" when trying to access server-manager (or any of the domains I'm hosting.)
The good news is that email is still working.
Further ideas?
-
try
/sbin/e-smith/signal-event console-save
or
/sbin/e-smith/signal-event post-upgrade
and
/sbin/e-smith/signal-event reboot
then.
this should rebuild ALL the templated configuration files and do full restart
-
Boris,
I tried:
/sbin/e-smith/signal-event console-save
then:
/sbin/e-smith/signal-event reboot
and had the same problems immediately after rebooting. Then, I tried to log in again about 20 minutes later and found things working fine. Go figure!
Not sure what worked, but thanks so much for your help, Boris.
-
It could be cache was serving the old content