I am trying to diagnose an intermittant fault with SignalR, so I want to enable tracing. I followed this guide
http://www.asp.net/signalr/overview/testing-and-debugging/enabling-signalr-tracing
However it is not working or I cannot find the files which are being produced. The configuration in the example just lists the name of the file to log, but no path.
Is there anything else I need to do to get this working? For examples any settings on IIS or additional configuration?
If it is working where would the files be written to?
I am using SignalR 2.1.2 and running it in IIS 7.5
I had to set permissions on the folder the trace file was attempting to write to for the application pool the signalr service is running in. For example the user for the application pool is
IIS APPPOOL\<Application Pool Name>
Related
I'm running jira in openshift using the basic image from atlassian: https://hub.docker.com/r/atlassian/jira-software
So far most things work fine.
I installed a plugin using the web ui which worked as well.
But now I'm running into an issue when a pod is restarted. The pod uses the image and naturally (as specified) my plugin is not installed anymore. I can install the plugin via webservice calls and register it as an osgi module for jira. But I don't want to do this manually. Building a pipeline or jon for this is quite easy (I'm thinking jenkins or ansible tower). But I so far I didn't find a way to trigger this pipeline after the pod is started (or better after jira is started).
Anyone got an idea how to handle this?
Thanks and best regards. Sebastian
Why not create a custom image based on the Atlassian image with everything you need installed?
As far as I know, there isn't a way to trigger a pipeline when a Pod is started; only Webhook, Image Change, and Config Change triggers are available. You'll need to write a Jenkinsfile to script all of the installation and setup you want, but then that can be triggered in one of the three ways mentioned.
I'm thinking an Image Change trigger would work best for you, so when the latest version of Atlassian's image comes out, you can run your pipeline to set everything up on the latest version.
Also, just curious, but do you have some persistent storage attached to the Jira pod? If not, you'll lose everything in Jira if the Pod dies; that means tickets, boards, comments, everything.
Update:
Looking at this page, it looks like most of the stuff you're trying to persist is stored in jira-home, so maybe mounting that as a persistent volume will be a good solution for you.
You're correct that the tickets are stored in the database, but I'm guessing the database connection settings are getting wiped when the Pod is cycled.
The jira-home directory stores your application and database connection settings, as well as a subdirectory for your plugins.
dbconfig.xml
This file (located at the root of your JIRA home directory) defines
all details for JIRA's database connection. This file is typically
created by running the JIRA setup wizard on new installations of JIRA
or by configuring a database connection using the JIRA configuration
tool.
You can also create your own dbconfig.xml file. This is useful if you
need to specify additional parameters for your specific database
configuration, which are not generated by the setup wizard or JIRA
configuration tool. For more information, refer to the 'manual'
connection instructions of the appropriate database configuration
guide in Connecting JIRA to a database.
jira-config.properties
This file (also located at the root of your JIRA home directory)
stores custom values for most of JIRA's advanced configuration
settings. Properties defined in this file override the default values
defined in the jpm.xml file (located in your JIRA application
installation directory). See Advanced JIRA configuration for more
information.
In new JIRA installations, this file may not initially exist and if
so, will need to be created manually. See Making changes to the
jira-config.properties file for more information. This file is
typically present in JIRA installations upgraded from version 4.3 or
earlier, whose advanced configuration options had been customized
(from their default values).
plugins/
This is the directory where plugins built on Atlassian's Plugin
Framework 2 (i.e. 'Plugins 2' plugins) are stored. If you are
installing a new 'Plugins 2' plugin, you will need to deploy it into
this directory under the installed-plugins sub-directory.
'Plugins 1' plugins should be stored in the JIRA application
installation directory.
This directory is created on JIRA startup, if it does not exist
already.
An ASP.NET application (running on Windows server/IIS 7) has to transfer big size files uploaded by current user to an external SFTP server. Due to the file size the idea is to do this asynchronously.
The idea is that the ASP.NET application stores the uploaded file on a local directory of the Windows server. The current user can continue his work. A Windows service or a Quartz job (other tools(*)/ideas?) is now responsible to transfer the file to the external SFTP server.
(*) Are there existing tools that listen on changes of a Windows directory and then move the files on a SFTP server (incl. handling communication errors/retries)?
If there is no existing solution, do you have had similar requirements? What do we have to consider? Because the connection to the SFTP server is not very stable we need an optimized error handling with auto retry functionality.
To watch for changes in a local directory in .NET, use
the FileSystemWatcher class.
If you are looking for an out of the box solution, use the keepuptodate command in WinSCP scripting.
A simple example of WinSCP script (e.g. watch.txt):
open sftp://username:password#host/
keepuptodate c:\local_folder_to_watch /remote_folder
exit
Run the script like:
winscp.com /script=watch.txt
Though this works only, if the uploaded files are preserved in the remote folder.
(I'm the author of WinSCP)
I have a problem with configuring standalone custom registry in WebSphere Application Server (Cluster environment). I have followed all steps from IBM manual:
I have implemented UserRegistry interface in DataBaseRegistry class
I have copied .jar to the lib/ext folder of WebSphere
I have assigned all necessary properties on Global Security page
and while trying to assign Standalone Custom Registry as current I got a following error:
Validation failed: Error occurred in RequiredModelMBean while trying to invoke operation getUsers
The funny part is that I followed all of those steps in a standalone version of WebSphere (not clustered) and it is working properly (so the problem is not in the code). Another thing is that there is nothing in the log files. I can see that getUsers is called and then no Exception or anything.
UPDATE: I resolved my problem. I was propably not 100% focused.
It tourned out that I forgot to copy additional jar with JDBC drivers to lib/ext that allow to connect to MSSQL.
LESSON LEARNED: Do not start important configuration work on Friday after lunch ;)
I have download packages laravel 5, and upload it on host http://test.dntc.com.vn/ for test
Result is blank page, no content.Help...
Check your server error_log for exact cause. Often there are storage folder permissions issues or Laravel Apache requirements are not installed.
Read more about requirements from http://laravel.com/docs/5.0/installation#server-requirements
First, enable PHP errors in your server to see whats happen.
I have installed the Bolt CMS on a Windows 2008 R2 server and it shows me a blank screen when I first try to launch it. I'm using IIS as the web server and MySQL as the database. I have verified that file permissions are set correctly for the folders that should be writable. PHP is also configured and working, and I have created my database and put the connection details into the config-yml-dist file. From my understanding the config.yml-dist file should be automatically renamed to config.yml when I run the application for the first time, but that isn't happening, in case that helps to know.
Can someone confirm if Bolt is compatible with Windows, and if so, provide any input on what I can check next?
Thanks.
I know a few websites with Bolt running on IIS / Windows 2008. If you're getting a blank screen, that means PHP is configured to not display errors. Which is the preferred setting for production servers, but not very convenient for development.
Either edit the php.ini file to 'display errors', or look in the server's error log for error messages. That should hopefully tell you what's going on.