cancel
Showing results for 
Search instead for 
Did you mean: 
trondah
Level 7

15004 binary is not yet available

Jump to solution

Hi,

We've got two virtual machines sharing the same policy through central management. Today I rebooted both nodes and suddenly I can not access any sites because URL filter can not be loaded, block code is 15004.

Looking at the mwg-core.errors.log I see this getting spammed on both nodes:

mwg-errors/mwg-core.errors.log:[2013-07-09 13:30:10.454 +02:00] [URLPlugin] [TSBinaryDoesNotExist] TS library is not yet available. In function 'virtual bool CTrustedSourceLibPro

xy::InitProcAddresses()'.

mwg-errors/mwg-core.errors.log:[2013-07-09 13:30:11.466 +02:00] [URLPlugin] [TSBinaryDoesNotExist] TS library is not yet available. In function 'virtual bool CTrustedSourceLibPro

xy::InitProcAddresses()'.

mwg-errors/mwg-core.errors.log:[2013-07-09 13:30:11.467 +02:00] [URLPlugin] [TSBinaryDoesNotExist] TS library is not yet available. In function 'virtual bool CTrustedSourceLibPro

xy::InitProcAddresses()'

Looking one day back in the log I also see this:

mwg-errors/mwg-core.errors1307090000.log.gz:[2013-07-08 14:51:52.029 +02:00] [URLPlugin] [Errno] Error while calling 'rename (old name: /opt/mwg/temp/mwg-coordinator_tempdir1373287905-8/libts.so, new name: /opt/mwg/plugin/data/URL/bin3/libts.so)'. Errorcode: '18' - 'errno: 18 - 'Invalid cross-device link''.

mwg-errors/mwg-core.errors1307090000.log.gz:[2013-07-08 14:51:52.029 +02:00] [URLPlugin] [UpdateFailed2] Error updating the com.scur.engine.trustedsource engine. Reason: 'Could not copy binary for update. Source: '/opt/mwg/temp/mwg-coordinator_tempdir1373287905-8/libts.so'. To: '/opt/mwg/plugin/data/URL/bin3/libts.so''.

mwg-errors/mwg-core.errors1307090000.log.gz:[2013-07-08 16:54:16.502 +02:00] [URLPlugin] [Errno] Error while calling 'rename (old name: /opt/mwg/temp/mwg-coordinator_tempdir1373295249-15/libts.so, new name: /opt/mwg/plugin/data/URL/bin4/libts.so)'. Errorcode: '18' - 'errno: 18 - 'Invalid cross-device link''.

mwg-errors/mwg-core.errors1307090000.log.gz:[2013-07-08 16:54:16.502 +02:00] [URLPlugin] [UpdateFailed2] Error updating the com.scur.engine.trustedsource engine. Reason: 'Could not copy binary for update. Source: '/opt/mwg/temp/mwg-coordinator_tempdir1373295249-15/libts.so'. To: '/opt/mwg/plugin/data/URL/bin4/libts.so''.

When I set up my appliances, I mounted separate partitions on /opt/mwg/temp and /opt/mwg/log. I'm wondering if this could have messed something up somehow.

Triggering an engine update does not rectify this problem. What to do???

on 7/9/13 7:42:20 AM CDT
0 Kudos
1 Solution

Accepted Solutions
fschulte
Level 10

Re: 15004 binary is not yet available

Jump to solution

My advise was a bit short. You should have done a "service mwg-core stop" before deleting the plugin/data/URL/ folder and afterwards a "service mwg-core start". But for now, a "service mwg-core restart" should bring MWG back to the normal stable state.

0 Kudos
6 Replies
fschulte
Level 10

Re: 15004 binary is not yet available

Jump to solution

Hi trondah!

First of all: Using an own partition layout for MWG is not supported.

The problem you see is a direct aftereffect: Updating engines in MWG use the file system function "rename" which only works within the same partition. The effect is, that the filter engines do not get their updates (in this case the first error you see is the missing GTI/Trusted Source library that cannot be installed and the URL Filter complains about the "missing binary").

To fix your problem, please unmount the partitions. (Maybe it will work for the log partition (keep in mind that this is still not supported! watch out for anomalies)).

Ciao

Felix

0 Kudos
trondah
Level 7

Re: 15004 binary is not yet available

Jump to solution

That's too bad, having everything in one filesystem is bad because log files or downloads can potentially fill up the drive preventing writes.

Anyways, unmounting the temp directory does not fix the problem. Triggering an update does nothing, I guess it thinks it's updated even though the last update failed.

0 Kudos
fschulte
Level 10

Re: 15004 binary is not yet available

Jump to solution

Can MWG now write into the /opt/mwg/temp/ folder?

Try to reset the plugin folders so that a new clean update can be downloaded. I.e. delete the folder /opt/mwg/plugin/data/URL/, trigger an engine update, and see if it works (you should get a full new URL filter update).

0 Kudos
trondah
Level 7

Re: 15004 binary is not yet available

Jump to solution

Yes it can. Removing URL and updating does not seem to work, now just spits out "[2013-07-09 16:12:22.447 +02:00] [URLPlugin] [GenericURLFilterError] Generic URL filter error. Reason: 'directory does not exist: '/opt/mwg/plugin/data/URL''.

0 Kudos
fschulte
Level 10

Re: 15004 binary is not yet available

Jump to solution

My advise was a bit short. You should have done a "service mwg-core stop" before deleting the plugin/data/URL/ folder and afterwards a "service mwg-core start". But for now, a "service mwg-core restart" should bring MWG back to the normal stable state.

0 Kudos
trondah
Level 7

Re: 15004 binary is not yet available

Jump to solution

Ok I see. I already went ahead and reinstalled my nodes, decided it was a good opportunity to test the restore functionality (which worked great!) Anyways, good to know.

0 Kudos