I am not able find the mpcontrol.log in one of site server.
Searched in location E:\SMS_CCM\Logs ,but failed get the log.Actually What is the purpose of the folder SMS_CCM?
[Please check below screenshots]
From which drive and which folder i can get the log.
Check E:\SMS\Logs.
Note that the mpcontrol.log file will only exist on your management point, not your distribution points (not sure if they're one and the same in your infrastructure, just going by the info provided)
Related
Can somebody tell me where I can set the path for the application log files which are on the Oracle application server because I can't find nothing in the web.
For an example I have a web app which I have been deployed on the server and this one have redirect errors output log and my question is from where the file path of the log is set?
Thanks in advance.
I'm not sure what you're looking for, but sounds like you need the OPMN configurations.
These can be found usually (and depends on your version) in 'ORACLE_HOME/opmn/conf/'.
The file you probably want is 'opmn.xml'
Here is a link for some documentation
Normally, after we create profiles both DMGR and Node, we have folder applications under path $DMGRPROFILE_HOME/config/cells/$cellName and installedApps under path $NODEPROFILE_HOME/.
All the applications to be deployed will be put into folder installedApps. And we can also see the same contents under the folder applications above. So my question is what's the difference between them? why does the websphere application server put such apps into folder applications besides installedApps?
what's more, for example, if i need to update one file named web.xml of my deployed application war file, do i have to update file under both path above?
Thanks in advance
The applications path under the Dmgr profile contains the files that have been deployed in the admin console.
The installedApps path under the Node profile contains those files after they've been synchronized out to each node. In most cases, this will be immediately after the deployment as well.
Deploying a single file
The safest practice would be to deploy a single file using the admin console, rather than editing it in-place on the filesystem:
The downside is that you have to enter the entire path to the server-deployed file name. e.g. webapp.war/WEB-INF/classes/com/yourcompany/project/package1/YourClass.class.
If you have a typo, it will deploy, but not where you wanted, and you might not notice it until your expected changes didn't take effect.
Direct edit on the filesystem
That said, it is faster to edit on the filesystem, so we do that at times especially for like JSPs. To do that, you need to edit the copy under the Node's installedApps directory. (The location is controlled by WebSphere variable APP_INSTALL_ROOT, which defaults to ${USER_INSTALL_ROOT}/installedApps.)
web.xml
web.xml, however, is different. If you edit that in installedApps, the changes won't take effect. Instead, you'll need to edit the one in a path something like:
$NODEPROFILE_HOME/config/cells/cellName/applications/earName.ear/deployments/applicationName/warName.war/WEB-INF
Or do it in the $DMGRPROFILE_HOME and then synchronize the node (either through syncNode.sh or through the admin console).
Either way, you'll then need to restart the enterprise application.
I got a Nexus OOS instance with the following settings:
proxy of the http://repo1.maven.org/maven2/
I override the "local storage location" with a path to a network device
Everything is ok and my Nexus instance works fine... but I notice the number of inodes grows a lot.
After a little check, I can tell every inodes come from the proxy/attributes/ directory.
According to the documentation:
Stores data about the files contained in a remote repository. Each
proxy repository has a subdirectory in the proxy/attributes/ directory
and every file that Nexus has interacted with in the remote repository
has an XML file which captures such data as the: last requested
timestamp, the remote URL for a particular file, the length of the
file, and the digests for a particular file among other things. If you
need to backup the local cached contents of a proxy repository, you
should also back up the contents of the proxy repository's directory
under proxy/attributes/.
Ok I understand why there is a lot of little files in this location but I have a dummy question: to avoid to reach my inode limit, could I periodically clean up the content of proxy/attributes/, without breaking anything and does these files will be recreated 'on demand' if needed?
I find nothing about it...
Any clue will be greatly appreciated!
You can find details on the contents of the working folder here: https://docs.sonatype.com/display/SPRTNXOSS/Nexus+Workspace+Directories+Analysis
The part you're specifically interested in is this:
/Proxy: This folder contains an "attributes" subfolder, that holds as
many subfolders as many repos you have (repoId is the name of
these). This is the place where "item attributes" are persisted as lots
of very small files. These files contain information about expiration
status and are consulted during proxying. Therefore, they have impact
on proxy and group lookup speed if stored on a slow disk. These files
are recreated on demand if they are missing or corrupted and thus
don't need to be backed up.
Hope that helps, if you need more realtime assistance, feel free top hop onto the user list or irc: http://nexus.sonatype.org/project-information.html
A PHP scriptof mine wants to write into a log folder, the resulting error is:
Unable to open the log file "E:\approot\framework\log/dev.log" for writing.
When I set the writing permissions for the WebRole User RD001... manually it works fine.
Now I want to set the folder permissions automatically. Is there an easy way to get it done?
Please note that I'm very new to IIS and the stuff around, I would appreciate precise answers, thx.
Short/Technical Response:
You could probably set permissions on a particular folder using full-trust and a startup taks. However, you'd need to account for a stateless OS and changing drive letters (possible, not likely) in this script, which would make it difficult. Also, local storage is not persisted, so you'd have no way to ensure this data stayed in the case of a reboot.
Recommendation: Don't write local, read below ...
EDIT: Got to thinking about this, and while I still recommend against this, there is a 3rd option: You can allocate local storage in the service config, then access it from PHP using a dll reference, then you will have access to that folder. Please remember local storage is not persisted, so it's gone during a reboot.
Service Config for local:
http://blogs.mscommunity.net/blogs/dadamec/archive/2008/12/11/azure-reading-and-writing-with-localstorage.aspx
Accessing config from php:
http://phpazure.codeplex.com/discussions/64334?ProjectName=phpazure
Long / Detailed Response:
In Azure, you really are encouraged to approach things as a platform and not as "software on a server". What I mean there is that ideas such as "write something to a local log file" are somewhat incompatible with the cloud "idea". Depending on your usage, you could (and should) convert this script to output this data to some cloud-based or external storage, vs just placing it on the disk.
I would suggest modifying this script to leverage the PHP Azure SDK and write these log entries out to table or blob storage in Azure. If this sounds good, please provide the PHP and I can give an exact example.
The main reason for that (besides pushing the cloud idea) is that in Azure, you cannot assume the host machine ("role instance") will maintain an OS state, so while you can set some things such as folder permissions, you can't rely on them sticking that way. You have no real way to guarantee those permissions won't be reset when the fabric has to update your role and react to some lower level problem. For example, a hard-drive cage on the rack where your current instance lives could fail. If the failure were bad enough, the Fabric controller would need to rebuild your instance. When that happens, your code is moved to an entirely different server, so the need would arise to re-set those permissions. Also, depending on the changes, the E:\ could all of a sudden need to be the F:\ or X:\ drive and you wouldn't know.
Its much better to pretend (at some level) that your application is running "in Azure" and not "on a server in azure", so you make no assumptions about the hosting environment. So anything you need outside of your code (data, logs, audits, etc) should be stored somewhere you can control (Azure Storage, external call-out, etc)
I am trying to add a rss feed into an HTML page. After some searching found something called simplepie.
On trying i get an warning
Warning: ./cache is not writeable.
Make sure you've set the correct
relative or absolute path, and that
the location is server-writable. in
xxx/inc/simplepie.inc on line 1780
On checking for the cache folder on the server i couldnt locate the folder. I am on a linux server. Would creating a cache folder be enough or do i need to get the hosting company to look into it
Thanks
In addition to creating the folder, you will need to make it writable by the user that the script will run as. You may need the hosting company's help on this. Otherwise, you can make it world-writable, though if you can restrict it to just allow the user the script runs as, then that would be best.