0.3.0 Issues & feedback...

Unimus support forum
Post Reply
wazza
Posts: 9
Joined: Thu Dec 15, 2016 1:33 am

Fri Feb 17, 2017 12:27 am

All,

So I got the email announcement. Raced to do a quick upgrade, and it's gone pretty smooth... (I would REALLY, like to avoid having to wipe the database again. That's more than a little tedious!)

So... After getting everything going again... I've got a few devices that are are not able to backup, they were under the last version. And I've got one that won't discover (again it was able to under the last version).

Few other points:-

* Search under Backups. It would be REALLY convenient to be able to search case insensitively and results come back for the description. (Same under Devices!)
* Would it be possible to have say a flag, under Devices, that indicated if there was a backup present for the device, and a different indicator showing that it was say less than (greater than might be better) a week old?
* Notifications at least via emails are working. It would be nice if it displayed more than just the one line!
* The log file is great. At least I can keep an eye on that, and it shows some basic diagnostic info, not that it's particularly useful to me.

Looking good though! Look forward to the next version!

Thanks,
Warren
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Fri Feb 17, 2017 1:04 am

wazza wrote:I would REALLY, like to avoid having to wipe the database again. That's more than a little tedious!
We promise this was the last time.
We have implemented an automatic database upgrade system now and it will be used by all future releases from now on.
wazza wrote: So... After getting everything going again... I've got a few devices that are are not able to backup, they were under the last version. And I've got one that won't discover (again it was able to under the last version).
What device types are not being backed-up?
Is the issue that they are discovered, just not backed-up?
Whats the error in the job history on the Dashboard?

Same questions for the device thats not being discovered.
wazza wrote: * Search under Backups. It would be REALLY convenient to be able to search case insensitively and results come back for the description. (Same under Devices!)
There is currently a bug with uppercase search:
https://tracker.unimus.net/browse/UN-65

It will be fixed in 0.3.1
wazza wrote: * Would it be possible to have say a flag, under Devices, that indicated if there was a backup present for the device, and a different indicator showing that it was say less than (greater than might be better) a week old?
We are always happy to add anything that helps with fast visualization and makes the system more user-friendly.
We will experiment with something and try to include it in 0.3.1
wazza
Posts: 9
Joined: Thu Dec 15, 2016 1:33 am

Fri Feb 17, 2017 2:40 am

Thanks for the quick response.

Okay the following is a device (Cisco 7301 router), that is discovered okay, but backup fails:-

Code: Select all

2017-02-17 13:30:13.936  INFO 570 --- [http-nio-8080-exec-37] net.unimus.service.DeviceService         : Attempt to run 1 backup(s)
2017-02-17 13:30:14.005  INFO 570 --- [http-nio-8080-exec-37] net.unimus.business.core.Core            : Performing backup on 1 device(s)
2017-02-17 13:30:34.345  WARN 570 --- [backup-54] n.u.c.d.cisco.CiscoSmbBackupDriver       : Unable to download backup - 'Expect operation fails (timeout: 20000 ms) for matcher: anyOf(regexp('\Qi3-lns1\E[>#] ?$'),regexp('More: .+ Quit: .+ $'))'!
I've got a few of those, all with the same result..

This is a Mikrotik (RB1100AHx2), which was discoverable and backupable in the last version. Won't discover:-

Code: Select all

2017-02-17 13:32:34.363  INFO 570 --- [http-nio-8080-exec-33] net.unimus.service.DeviceService         : Attempt to run 1 discover(y/ies)
2017-02-17 13:32:34.402  INFO 570 --- [http-nio-8080-exec-33] net.unimus.business.core.Core            : Performing discovery on 1 device(s)
This one is a Ubiquiti ToughSwitch, which is discoverable, but not backupable (wasn't under the last version either):-

Code: Select all

2017-02-17 13:35:27.915  INFO 570 --- [http-nio-8080-exec-40] net.unimus.service.DeviceService         : Attempt to run 1 backup(s)
2017-02-17 13:35:27.973  INFO 570 --- [http-nio-8080-exec-40] net.unimus.business.core.Core            : Performing backup on 1 device(s)
2017-02-17 13:35:27.982 ERROR 570 --- [backup-56] o.s.integration.handler.LoggingHandler   : org.springframework.messaging.MessageHandlingException: nested exception is java.lang.IllegalArgumentException: Device type 'TOUGHSwitch' not supported by any SSH backup drivers
        at org.springframework.integration.handler.MethodInvokingMessageProcessor.processMessage(MethodInvokingMessageProcessor.java:96)
        at org.springframework.integration.handler.ServiceActivatingHandler.handleRequestMessage(ServiceActivatingHandler.java:89)
        at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:109)
        at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:127)
        at org.springframework.integration.dispatcher.AbstractDispatcher.tryOptimizedDispatch(AbstractDispatcher.java:116)
        at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:148)
        at org.springframework.integration.dispatcher.UnicastingDispatcher.access$000(UnicastingDispatcher.java:53)
        at org.springframework.integration.dispatcher.UnicastingDispatcher$3.run(UnicastingDispatcher.java:129)
        at org.springframework.integration.util.ErrorHandlingTaskExecutor$1.run(ErrorHandlingTaskExecutor.java:55)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Device type 'TOUGHSwitch' not supported by any SSH backup drivers
        at net.unimus.core.service.cli.CliBackupService.backup(CliBackupService.java:59)
        at net.unimus.core.service.BackupService.backup(BackupService.java:38)
        at net.unimus.core.configuration.MessageFlowConfiguration$3.handle(MessageFlowConfiguration.java:77)
        at sun.reflect.GeneratedMethodAccessor810.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:113)
        at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:102)
        at org.springframework.expression.spel.ast.MethodReference.access$000(MethodReference.java:49)
        at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:347)
        at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:88)
        at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:131)
        at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:330)
        at org.springframework.integration.util.AbstractExpressionEvaluator.evaluateExpression(AbstractExpressionEvaluator.java:169)
        at org.springframework.integration.util.MessagingMethodInvokerHelper.processInternal(MessagingMethodInvokerHelper.java:317)
        at org.springframework.integration.util.MessagingMethodInvokerHelper.process(MessagingMethodInvokerHelper.java:155)
        at org.springframework.integration.handler.MethodInvokingMessageProcessor.processMessage(MethodInvokingMessageProcessor.java:93)
        ... 11 more
Thanks for looking into these. If you need other diags, let me know.

Rgds,
W.
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Fri Feb 17, 2017 3:01 pm

Tickets created, fixes in progress.
https://tracker.unimus.net/browse/UN-137
https://tracker.unimus.net/browse/UN-139
https://tracker.unimus.net/browse/UN-140

All of these will be fixed in 0.3.1 - which will be a hotfix release Monday/Tuesday next week.

If you find any more issues, please let us know!
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Sat Feb 18, 2017 7:17 pm

I could not replicate MikroTik discovery not working.
(I tested on multiple models of RB, as well as CHR and x86)

What error are you getting on the MikroTik discovery failure in the Failed Jobs Log on the Dashboard?
wazza
Posts: 9
Joined: Thu Dec 15, 2016 1:33 am

Sat Feb 18, 2017 10:52 pm

Error on the dashboard is:-

telnet_unavailable
ssh_unavailable

I have confirmed that both telnet and ssh are definitely open and respond, from the Unimus machine, on the standard ports (23 & 22 respectively).

We do often use alternate ports for these services, but NOT in this case.

Thanks,
W.
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Sun Feb 19, 2017 5:27 pm

Can you please contact me over PM to organize some kind of remote session to debug this issue?

Thanks!
Post Reply