It’s possible Backup is running the modprobe command (or lsmod) to verify 
drivers for tape robots/drives and/or SCSI drivers for same are there but that 
doesn’t change what I said about it being an OS level issue.   If the backups 
are running successfully it would seem it is finding the driver(s) needed for 
backups.

Did you try the “cat –vt” on modprobe.conf?

What does lsmod show?

You might want to type “man modprobe” to get more details of the command.


From: men [mailto:[email protected]]
Sent: Thursday, December 04, 2014 11:51 AM
To: Lightner, Jeff; aaa aaa
Subject: RE: [Veritas-bu] wield messages on /var/log/messages after install 
BACKEXEC


I know what you say but those messages pop-up on:

1. while I install BACKEXEC agent
2. every time BACKEXEC perform backup.
3. wield thing is modprobe.conf file did not change by BACKEXEC.  it is correct 
and old time stamp.

________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Date: Thu, 4 Dec 2014 16:28:31 +0000
Subject: Re: [Veritas-bu] wield messages on /var/log/messages after install 
BACKEXEC
This isn’t really a backup question but rather a RHEL5 Linux question.   For 
such  questions you’d be better off going to one of the various Linux forums 
(or to RedHat’s own forums) in the world.    A popular one is 
linuxquestions.org but there are many others.

modprobe in Linux is used to install/remove kernel modules.

What you’re seeing is gobbledegook which suggests your modprobe.conf file 
contains some corruption.

First thing I’d do is verify none of the filesystems are full.

If you run “cat –vt” on modprobe.conf you can see where the weird items are.

Essentially you’d have to clean up the file to get rid of this stuff but before 
doing that you should get some expert assistance.   You can call RedHat if you 
have a valid subscription or post to one of the forums I mentioned.

Since your system is up and running it appears the corrupted lines aren’t 
hurting but they should be cleaned up.   Often what you’ll see is that a valid 
entry has these bogus characters somewhere in the line.


From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of men
Sent: Thursday, December 04, 2014 10:41 AM
To: aaa aaa
Subject: [Veritas-bu] wield messages on /var/log/messages after install BACKEXEC

we have REDHAT 5.X on DELL servers.  Recently we upgrade to BACKEXEC  later 
version of software and /var/log/messages have following messages:
Dec  3 18:19:04 ORA1 modprobe: WARNING: Unmatched bracket in ÷     0E[rŠ£½Øô/N
Dec  3 19:14:45 ORA1 modprobe: WARNING: Unmatched bracket in •§ºÎãù(A[v’¯Íì
Dec  3 19:14:45 ORA1 modprobe: WARNING: Unmatched bracket in ÈÚí,C[tŽ©Åâ
Dec  3 19:14:45 ORA1 modprobe: WARNING: Unmatched bracket in `r…™®ÄÛó
                                                                          &A]z˜·
Dec  3 19:29:45 ORA1 SYMBDSNAP_SDK[7808]: Reloc File successfully created.
Dec  3 19:30:38 ORA1 SYMBDSNAP_SDK[7808]: Reloc File successfully created.

ANy one know why?
Thanks

_______________________________________________ Veritas-bu maillist - 
[email protected]<mailto:[email protected]> 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________ Veritas-bu maillist - 
[email protected]<mailto:[email protected]> 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to