Error Occurred During Initialization Could Not Read Logging Configuration File
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Getting the error message "<16> bpbrm main: Error occurred during initialization. Could not read logging configuration file" when backing up a client under AIX6.1. Article:000040164 Publish: Article URL:http://www.veritas.com/docs/000040164 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Getting the error message "<16> bpbrm main: Error occurred during initialization. Could not read logging configuration file" when backing up a client under AIX6.1. Solution Getting the error message below when backing up a client under AIX 6.1. though the backup is done successfully: <16> bpbrm main: Error occurred during initialization. Could not read logging configuration file Exact Error Message: This message can be seen in the backup job details from the GUI or the CLI as below: # /usr/openv/netbackup/bin/admincmd/bperror -jobid
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : https://www.veritas.com/support/en_US/article.000040164 Error occurred during initialization. Could not r... VOX : Backup and Recovery : NetBackup : Error occurred during initialization. Could not r... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Error occurred during initialization. https://vox.veritas.com/t5/NetBackup/Error-occurred-during-initialization-Could-not-read-logging/td-p/676956 Could not read logging configuration file. lanira_1509 Level 4 05-27-2014 10:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi every body, As the title indicates, I have this message on my Media Server which is also the Master Server.(NetBackup 7.0.1) In the bpdm log Here the details : 14:04:33.379 [7760.6476] <16> initialize: Error occurred during initialization. Could not read logging configuration file. 14:04:33.394 [7760.6476] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172004 -jm 14:04:33.394 [7760.6476] <2> main: Sending [EXIT STATUS 0] to NBJM 14:04:33.394 [7760.6476] <2> bptm: EXITING with status 0 <---------- 14:14:33.382 [6000.8320] <16> initialize: Error occurred during initialization. Could not read logging configuration file. 14:14:33.382 [6000.8320] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172009 -jm 14:14:33.397 [6000.8320] <2> main: Sending [EXIT STATUS 0] to NBJM 14:14:33.397 [6000.8320] <2> bptm: EXITING with status 0 <---------- 14:24:33.385 [5968.4128] <16> initialize: Error occurred du
not read logging configuration file Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] After this http://mailman.eng.auburn.edu/pipermail/veritas-bu/2008-March/048049.html issue I did some other RHEL5 installations and didn't see the issue on those hosts. Differences between those installations and this one were: 1) I had gone http://www.logalyze.com/support/release-notes into the GUI host properties for Master and set this client to use ports for firewall as we'd previously done with 5.1. On the new clients error occurred it defaults to vnetd in firewall configuration so this wasn't necessary. On removing this setup after the other installs it didn't resolve the issue by itself but I mention it as it *might* be part of the solution. 2) During my initial attempt to do backup on the RHEL5 host it had failed on error occurred during missing library, /usr/lib/libstdc++-libc6.2-2.so.3. This was because the compat-libstdc++-296 package wasn't installed. Installation of that package made the backup work but I got the error noted in original message. On all the new hosts I installed compat-libstdc++-296 before installing NBU 6.0 MP4 client. I believe item 2 was what actually fixed it. On the original host I removed the installation then reinstalled (this means the compatibility library was already there on reinstall of NBU). After reinstall the backup worked without giving the bpbrm error. Also I noticed on all the successful installs including this reinstall it creates the /usr/openv/logs directory and creates log with a header. It hadn't done that during my initial install on the problem host. ________________________________ From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Jeff Lightner Sent: Tuesday, March 04, 2008 6:22 PM To: VERITAS-BU at mailman.eng.auburn.edu Subject: [Veritas-bu] Could not read logging configuration file Trying to figure out the fix for this message: Error bp
SupportKnowledge BaseFAQBLOGalyzeRelease notes ResourcesDownloads Skip to content LOGalyze Search... You are here: Home Support Release notes Release notes Share TwitterVersion 4.1.2 - 2012-03-18 Bugs Log Definition with unknown function 'ncsa' was released in 4.1.1 Version 4.1.1 - 2013-03-13 Bugs LOGALYZE-71: Remove progress indicator if log in fails LOGALYZE-69: Display all value of field _tag in Search result Some CSS and layout fixes LOGALYZE-94: Fix error during Definition file saving LOGALYZE-66: Create new Statistic Definition: sometime store table was not created Updated Time zone list Fixed chart labels in PDF reports Some minor modifications and fixes Improvements API: New server side input validations Updated inline documentation for main configuration file Updated inline Collector Schema Documentation LOGALYZE-87: Reorderable Report sections Fix startup files on Windows Improved data aggregation New features New Index rolling frequency (half-day) New JVM parameters (rolling policy) in startup script LOGalyze Repository content is in the release package Known bugs Log Definition with missing NCSA parser Symptoms LOGalyze Engine does not start. Error message: ERROR LOGalyzeEngine Error occured during initialization of LOGalyze Engine. Startup aborted. com.logalyze.engine.config.ConfigException: Unknown function: ncsa Cause There is a wrong Log Definition file in conf/repository/ folder called ddb67bfe-ae5a-11e1-88ed-0018de9d2512.xml. This file contains a parser (ncsa) which is missing from 4.1.1 Resolution Simply remove this file or rename it to ddb67bfe-ae5a-11e1-88ed-0018de9d2512.xml.disabled Version 4.1.0 - 2012-10-25 - Open Source Release This version is the first Open Source Release of LOGalyze released under LGPL v3. Version 4.0.3 - 2012-07-25 Bugs Collectors: Identity type collector is added Dashboard: Fix layout bug in ChartPortlet Statistics: dimension value is truncated to 128 chars Statistics: line chart margin is fixed Statistics: ability to select dimension to display Statistics: SUM function was missing on New Statistics Definition page Improvements Common colors: charts will use the same color for a given series every time New caching method for Grid components Charts: disable animation Index: loghostname field is cenverted to lowercase Search: new generated f