The site path route already exists

Hi,

sure, you can just rename the existing one.

Sabine

Thank you for your reply,

Already done that and everything working just fine.

Thanks

Sorry for hijacking this topic.

I know that this is marked as solved, but I'm experiencing this same problem on random virtual webserver entries since a month or so.

What might be interesting is that for the duplicates, one is listed as "/ (12)", and the other as "RealServerName: / (12)". When you open the last one, the name is displayed as "/ (12)" too, and the error is displayed when you try to save it.

So it turns out that for some reason duplicate site path routing entries are created, possible caused by a change in one of the last couple of updates.

Renaming one is a workaround, but not a solution for a bug that needs to be fixed imho.

Hi,

I tried to reproduce your issue but didn't manage.

Your configuration shouldn't be possible. How did you get there?

Sabine

I don't know, I never do anything with site paths manually.

You only notice you have this problem when you try to update a virtual webserver entry and try to save if, so I can't tell you how long it has been there. I even had three entries numbered "(5)". Two were displayed as "/ (5)"., one as "VirtualServername: / (5)".

I made screenshots:

All of these virtual webserver entries were created sometime in June, within the space of a week.

Which version did you run in June?

Very good question.

This particular firewall was installed from asg-9.402-7.1.iso at the end of May, and we have a maintenance window every two weeks, so there can't have been many updates waiting to be installed (currently there is 1 waiting which will be installed tomorrow night).

Is there a log somewhere that shows the installed updates?

You can find the infos in /var/log/up2date.log.

Was this a complete fresh Installation or did you restore an existing backup (if yes, from which version)?

This was a new installation, according to the up2date logs installed on 2016-05-17.

This was it's update sequence:

2016:05:24-15:32:30 firewall-1-1 auisys[14085]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.402007-403004.tgz.gpg
2016:05:24-15:32:30 firewall-1-1 auisys[14085]: unpacking up2date package version: 9.403004
2016:05:24-15:32:56 firewall-1-2 auisys[4814]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.402007-403004.tgz.gpg
2016:05:24-15:32:56 firewall-1-2 auisys[4814]: unpacking up2date package version: 9.403004
2016:06:28-09:56:30 firewall-1-1 auisys[3259]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.403004-404005.tgz.gpg
2016:06:28-09:56:30 firewall-1-1 auisys[3259]: unpacking up2date package version: 9.404005
2016:06:28-09:57:16 firewall-1-2 auisys[40794]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.403004-404005.tgz.gpg
2016:06:28-09:57:16 firewall-1-2 auisys[40794]: unpacking up2date package version: 9.404005
2016:08:05-02:24:51 firewall-1-2 auisys[62499]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.404005-405005.tgz.gpg
2016:08:05-02:24:51 firewall-1-2 auisys[62499]: unpacking up2date package version: 9.405005
2016:08:02-08:48:28 firewall-1-2 auisys[58034]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.404005-405005.tgz.gpg
2016:08:02-08:48:28 firewall-1-2 auisys[58034]: unpacking up2date package version: 9.405005
2016:08:02-08:48:46 firewall-1-1 auisys[10172]: unpacking up2date package: /var/up2date/sys/u2d-sys-9.404005-405005.tgz.gpg
2016:08:02-08:48:46 firewall-1-1 auisys[10172]: unpacking up2date package version: 9.405005

I can't recall when these webserver entries were created, but I am pretty sure it was before 2016-06-28.

To see the version history, type version at the command line.

Cheers - Bob