Forums

Rob Thorne
Rob Thorne
Offline
Resolved
0 votes
My ISP changed my circuit this morning, and I am now on a different network and a different fixed IP.

To get things working again, I changed /etc/sysconfig/ifcfg-eth0, just changing IPADDR and GATEWAY to point to the new network. After restarting the network service (directly, via "service network restart"), and editing my /etc/resolv-peerdns.conf to change the DNS servers, my ClearOS 6.5 system works as a gateway. Hosts inside my network can see out, and dig resolves DNS directories both on the ClearOS box and from my internal network.

But the webconfig web app can't get at my network settings. If I try the "IP Settings" link from the javascript drop-down, I get a text error screen that looks something like this:


Settings
Network Mode Gateway Mode
Hostname myaccount.mydomainname.com
Internet Hostname mymail.mydomainname.com
Default Domain mydomainname.com
Edit
Ooooops: Network interface is invalid.


I'm not clear what's wrong, and there isn't much there for me to debug.

I've changed the IP in the ClearOS secure site (my A record for the mail host), and in the myaccount.poweredbyclear.com screen. So mail at least is coming in. But I'd like to know what might be screwed up along with the "IP Settings" screen, and how I can get webconfig back in sync with everything else.

Anybody see this OOPS before?
Friday, April 11 2014, 07:28 PM
Share this post:
Responses (4)
  • Accepted Answer

    lukkes
    lukkes
    Offline
    Wednesday, July 15 2015, 02:28 PM - #Permalink
    Resolved
    0 votes
    i have the same problem today, and after check on "/etc/sysconfig/network-scripts" i found that after edit the config file "ifcfg-eth1" with joe editor, it create a backup file called "ifcfg-eth1~" this special character "~" make the web interface to not parse correctly and make the " OOOPSSS" just delete it, and works again.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 13 2014, 10:06 PM - #Permalink
    Resolved
    0 votes
    I would have done the same as you too so a little surprised that the webconfig threw up an exception

    The webconfig log should give further information (a debug back trace) on why this was the case? permissions problem? formatting / syntax?

    You can find sync actions at /etc/clearsync.d/ which monitor config changes and replicate them across the other services

    You normally just edit the external WAN IP by editing the interface through Network > IP settings :)
    The reply is currently minimized Show
  • Accepted Answer

    Rob Thorne
    Rob Thorne
    Offline
    Sunday, April 13 2014, 10:00 PM - #Permalink
    Resolved
    0 votes
    The problem here was that the ISP changed the static IP on me, and it wasn't initially obvious what was wrong. So eth0 had no connectivity at all, and it wasn't obvious how to change this in webadmin. Also: ClearOS's documentation is on the web, and eth0 being down, that was a lot of help just then :-)

    I know CentOS well, and changing the files in /etc/sysconfig/network-scripts was the obvious thing to do. Since I needed to get things up immediately (including my mail server), it was what I could do without access to the documentation.

    At least in earlier versions of ClearOS and ClarkConnect, it was possible to actually treat the system as if it was a CentOS server. Is this no longer the case?

    In any case: the format of /etc/sysconfig/network-scripts/ifcfg-eth0 was the same as the file I replaced (which I backed up). Only the static IP and the gateway were changed. In previous versions of the ClearOS software, this was a reasonable way to change the IP in these sorts of cases. If the IP lives anywhere else on ClearOS, I haven't found where it's documented. It needs to be.

    It would be good if said "sync actions" were accessible from the command line. If you'll tell me where to look, I'm PHP developer, and can hook up a remote debugger if I need to. I'd have done so on Friday if I had the time.

    Sometimes, folks who do web admin apps make things "too easy", and do it at the expense of transparency. This may be one of those cases.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 13 2014, 09:28 PM - #Permalink
    Resolved
    0 votes
    You should find further clues in /var/log/webconfig/error_log or /var/log/messages

    Why didn't you just use the webconfig to make the changes? otherwise the various 'sync' actions that keep everything sane will not happen
    The reply is currently minimized Show
Your Reply