VMware Cloud Community
TheBob1
Contributor
Contributor

VDP Upgrade from 6.1.10 to 6.1.11 not possible

Hello @ll,

i would like to upgrade from 6.1.10 to 6.1.11 but after mounting the new iso there are no upgrades shown on vdp-configure. I can see on Shell that the images is mounting ok and also follow this link: VMware Knowledge Base  but no upgrade are available.

The Restart of avintaller are get some error:

INFO: Stopping AVI...

09:02:18.947 [main] INFO  com.avamar.avinstaller.AVIMain - Loaded config properties...

09:02:18,886 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]

09:02:18,886 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]

09:02:18,886 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.xml]

09:02:18,887 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Setting up default configuration.

09:02:19,011 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]

09:02:19,011 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]

09:02:19,031 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

09:02:19,039 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]

09:02:19,041 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]

09:02:19,066 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used

09:02:19,067 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern /usr/local/avamar/lib/jetty//logs/jetty_%d{yyyy-MM-dd}.%i.log for the active file

09:02:19,069 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5e025e70 - The date pattern is 'yyyy-MM-dd' from file name pattern '/usr/local/avamar/lib/jetty//logs/jetty_%d{yyyy-MM-dd}.%i.log'.

09:02:19,069 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5e025e70 - Roll-over at midnight.

09:02:19,072 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5e025e70 - Setting initial period to Wed Jan 02 15:53:24 CET 2019

09:02:19,081 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property

09:02:19,082 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: /usr/local/avamar/lib/jetty//logs/jetty.log

09:02:19,082 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [/usr/local/avamar/lib/jetty//logs/jetty.log]

09:02:19,083 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO

09:02:19,083 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]

09:02:19,083 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT]

09:02:19,083 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.

09:02:19,083 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@c818063 - Registering current configuration as safe fallback point

java.net.ConnectException: Connection refused (Connection refused)

        at java.net.PlainSocketImpl.socketConnect(Native Method)

        at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)

        at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)

        at java.net.AbstractPlainSocketImpl.connect(Unknown Source)

        at java.net.SocksSocketImpl.connect(Unknown Source)

        at java.net.Socket.connect(Unknown Source)

        at java.net.Socket.connect(Unknown Source)

        at java.net.Socket.<init>(Unknown Source)

        at java.net.Socket.<init>(Unknown Source)

        at com.avamar.avinstaller.AVIJettyHelper.stop(AVIJettyHelper.java:43)

        at com.avamar.avinstaller.AVIMain.main(AVIMain.java:350)

Usage: java -jar start.jar [options]

       java -jar start.jar --help  # for more information

Avistart process:

INFO: Force to stop AVI...

kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Avistart process:

AvInstaller is already running

and there are no aviinstaller logs available.

Is there any one how has the same problem or can help me?

Thanks in advanced

TBC

Reply
0 Kudos
4 Replies
rjs74
Contributor
Contributor

Think I'm having the same issue. I can't get VDP appliances running 6.1.10 to detect the upgrade ISO for 6.1.11.

Anyone else?

Reply
0 Kudos
rjs74
Contributor
Contributor

OK, figured it out. This resolved the problem for me: VMware Knowledge Base

Reply
0 Kudos
JamesLenaburg
Contributor
Contributor

I have the problem.  Trying to upgrade 6.1.10.3 to 6.1.11 and cannot get it to recognize the upgrade ISO.

Followed the VM Knowledge Base article to the letter.  Doesn't work for me.

Any other ideas?

Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee

VDP is no longer supported, you might be better switching to an alternate backup and recovery solution now.


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos