Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[vSRX] Explanation of log messages seen during AIS installation

0

0

Article ID: KB30878 KB Last Updated: 27 Sep 2018Version: 4.0
Summary:

This article explains the log messages seen during AIS script installation on the VSRX platform. The log messages may seem like errors but they were created for cosmetic purposes.

Symptoms:

Example log messages that seem like errors:

root> request system scripts add jais-5.0R3.0-signed.tgz no-copy
grep: /etc/db/pkg/jais/+COMMENT: No such file or directory
Installing package '/cf/root/jais-5.0R3.0-signed.tgz' ...
Verified jais-5.0R3.0.tgz signed by PackageProductionEc_2016
Verified jais-5.0R3.0.tgz signed by PackageProductionRSA_2016
Adding jais...
Available space: 136444 require: 1838
Installing AI-Scripts version: 5.0R3
Saving package file in /var/db/scripts/commit/jais-5.0R3.0-signed.tgz ...
chmod: /var/db/scripts/commit/jais-5.0R3.0-signed.tgz: No such file or directory
ls: /var/tmp/jais-5.0R3.0-signed.tgz: No such file or directory
NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install
ln: ///etc/rc.d/ais: Read-only file system

Mounted jais package on /dev/md3...
Verified manifest signed by PackageProductionEc_2016
Verified jais-5.0R3.0 signed by PackageProductionRSA_2016
Model: vSRX
Linking in default manifest file.
Creating default trend data file.
Creating SRX intelligence attachments file.
Creating SRX events attachments file.
Creating AI-Scripts FIFO
Starting AI-Scripts FIFO handler
8001: old priority 0, new priority 20
RSI parameters are now being set
BIOS validation parameter is now being set
BIOS interval parameter is now being set
JMB cleanup age is now being set
JMB Event file is now being set
JMB User Event file is now being set
PHDC collect parameter is now being set
PHDC duration parameter is now being set
PHDC commands file is now being set
JMB Progress Logging parameter is now being set
iJMB generation parameters are now being set
chown: /var/db/scripts/op/day_dow_ijmb: Invalid argument
AI-Scripts platform support flag is now being set
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
Interval event commands file is now being set
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
Interval event enabled parameter is now being set
chown: /var/db/scripts/op/day_dow_cjmb: Invalid argument
chown: /var/db/scripts/op/rsi_collect_enabled: Invalid argument
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
chown: /var/db/scripts/op/bios_collect_enabled: Invalid argument
chown: /var/db/scripts/op/phdc_cmds_file: Invalid argument
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
RSI Lite Enabled is now being set
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
Removing any old files that need to be updated
Copying updated files
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
usage: chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhv] [-R [-H | -L | -P]] :group file ...
Restarting eventd ...
Event processing process started, pid 8242
Installation completed
Saving state for rollback ...

Solution:

 

  1. grep: /etc/db/pkg/jais/+COMMENT: No such file or directory

    When the package is created, the file +COMMENT is added if it exists. It does not always exist, so getting a message that it wasn't found is cosmetic.

  2. chmod: /var/db/scripts/commit/jais-5.0R3.0-signed.tgz: No such file or directory
    AND
    ls: /var/tmp/jais-5.0R3.0-signed.tgz: No such file or directory

    The chmod and ls messages are stating it did not find certain files it was either checking on or expected. It is not an error.

  3. NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install

    As part of the original code, the installation will save any configuration changes that have been made, but not committed to that point. In pre-5.0 code, after installation, it performs a commit to activate AI-Scripts since a SLAX commit script was used for this purpose. However, in 5.x and later, the commit command has been removed from the installer. This is because no commit script is used. Instead, a static configuration change is made on the initial installation of 5.0 by ServiceNow. After that, a commit is not needed for AI-Scripts. Thus, saving any configuration changes by the installer ends up being strictly cosmetic.

  4. ln: ///etc/rc.d/ais: Read-only file system

    The message regarding /etc/rc.d/ais is an artifact of having the same code repository generate code for both legacy Junos and BSDx Junos. This is a cosmetic message. Legacy Junos uses a different file for implementing AI-Scripts setup on reboot/Junos upgrade.

  5. chown: /var/db/scripts/op/day_dow_ijmb: Invalid argument

    This is specific to 15.1x and later versions which uses a different Junos architecture than older Junos versions. This message is cosmetic. It does not interrupt the installer. A further check will be added to AI-Script to detect the platform and not use chown for vSRX. Refer to PR1191094.

 

Modification History:

2018-09-27: Minor, non-technical edit

 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search