Blogs

When changing the guest OS password of root, you may encounter an Authentication token manipulation error. This message occurs because the /etc/shadow file is not present. You can add the shadow file by entering 'pwconv', then the root password can be set. See the example below.

bash-3.2# passwd
Changing password for user root.
passwd: Authentication token manipulation error

bash-3.2# pwconv
bash-3.2# passwd
Changing password for user root. ...Read More

 

In addition to bug fixes, AXP 1.6.2 adds support for the new SM-SRE-710-K9 and SM-SRE-910-K9 service modules. Additionally, the expiration check of the authorization bundle is no longer enforced in AXP 1.6.2. The authorization bundle, which is provided by Cisco Developer Network, grants permission to run applications on the AXP platform. In addition to security information, the authorization bundle also contains an expiration date. Starting from AXP 1.6.2, the check on this expiration date ...Read More

 

The AXP upgrade process provides key features such as automatic deletion of previously installed files that are not included in the upgrade package. However, in order to not delete previously installed files, the upgrade process requires that previously installed files be included in the upgrade package which can lead to bloated packages. To simply the package and reduce package size, users can create a patch to modify only intended files. For example, if the initial installed package contai ...Read More

 

AXP version 1.6.1 has added support for Simple Network Management Protocol SNMPv2c. SNMP commands used in Cisco AXP are similar to Cisco IOS software SNMP commands. The AXP User Guide provides examples of traps generated by agents in SNMP that are utilized by Cisco AXP. Please review the AXP User Guide section 'System Management using SNMP and CDP' along with the Command Reference Guide for more information.
...Read More

 

In addition to bug fixes, the AXP 1.5.2 maintenance release builds upon AXP 1.5.1- see the blog 'AXP 1.5.1 Release - A Giant Leap Forward' - by adding support for two new service modules. The SRE 700 has a 1.86 GHz cpu, 4 GB Ram, and a 500 GB HD. The SRE 900 offers Raid 1 support, has a 1.86 GHz dual core cpu, 4 GB RAM and 2x500 GB HD. Raid-1 and linear raid can be selected as options at install time. This new hardware runs on the new Cisco Generation 2 routers which require IOS re ...Read More

 

AXP takes a huge step forward by adding new hardware support and software features. I¿ll discuss many of the new hardware and features below.
...Read More

 

After downloading the provided AXP gzipped tar files for your service module, if you are using a windows environment, you might decide to untar the files with WinZip. If this choice is made, caution must be taken because WinZip has a 'TAR file smart CR/LF Conversion ...Read More

 

Showing 7 results.
Items per Page 20
of 1
First Previous Next Last

Forums

« Back to Technical Questions

Can't package using ver1.1.1's pkg_bundle.sh

Combination View Flat View Tree View
Threads [ Previous | Next ]
Post New Thread
Can't package using ver1.1.1's pkg_bundle.sh
Answer
10/21/08 10:44 AM
I've had the following problem. ( No problems with ver 1.0.4)
Pls tell me how to package correctly.

1. Packaging process doesn't progress at the specific step
//// Log ////
#
# /opt/axp-sdk.1.1.1/tools/pkg_build.sh
--project-dir '/source/ciscoapp/package' --auth-bundle
'/opt/axp-sdk.1.1.1/keys/auth_bundle.sig' --private-key
'/opt/axp-sdk.1.1.1/keys/private.key' --name 'ciscoapp' --version '1'
--description 'HelloWorld ver1' --source-dir '/source/ciscoapp/build'
--disk-limit '10M' --memory-limit '64M' --cpu-limit '1000'
--postinstall 'bin/post-install.sh'
SLIM Packaging Utility. (C) 2007 Cisco Systems, Inc
Checking dependencies...
Generated swap option: OFF
Creating project directories...
Generated Application UUID: 29027b4c-f830-4ddc-b2f0-d70e7f54dd51
Preparing configuration for the core packaging tool...
Creating runtime signatures...
Generating a list of files to package...
Preparing package manifest...
Processing manifest file information... <<<----- Here.
////////

2. At that step, [APP_BUILD_DIR]/package/pkg/core.log shows the following.
//// core.log ////
Replacing keywords in
/source/ciscoapp/package/templates/ciscoapp_manifest.template... done.
Replacing keywords in
/source/ciscoapp/package/templates/ciscoapp_package_spec.template...
done.
Replacing keywords in
/source/ciscoapp/package/templates/helloworld_manifest.template...
done.
Replacing keywords in
/source/ciscoapp/package/templates/helloworld_package_spec.template...
done.
Replacing keywords in
/source/ciscoapp/package/templates/pingapp_manifest.template... done.
Replacing keywords in
/source/ciscoapp/package/templates/pingapp_package_spec.template...
done.

Checking for installed files that are not in packaging file list...
The following files/directories in the install directory are missing
from packaging file list.
/opt/axp-sdk.1.1.1/lib/pkg/bin/fgrep: error while loading shared
libraries: libpcre.so: cannot open shared object file: No such file or
directory
/opt/axp-sdk.1.1.1/lib/pkg/bin/fgrep: error while loading shared
libraries: libpcre.so: cannot open shared object file: No such file or
directory
Do you wish to continue packaging without these files(y,n)? Please
answer y to continue, no to exit:
////////

Thanks in advance.
Makoto
Flag

Re: Can't package using ver1.1.1's pkg_bundle.sh
Answer
10/21/08 7:00 PM as a reply to Makoto Murakami.
I had the same issue on 2 different development machines.
The fix is to add in this sym link:
ln -s /lib/libpcre.so.0 /usr/lib/libpcre.so

More about the fix here:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ax/1.0/release/notes/axprn.html#wp46007

Edited by: carl.j.hanks.boeing.com on Oct 21, 2008 10:00 AM
Flag

Re: Can't package using ver1.1.1's pkg_bundle.sh
Answer
10/22/08 2:30 PM as a reply to Makoto Murakami.
Thanks for your help.
It works fine!


Makoto
Flag

Collateral


No files available