The system tray icon for my Incredibuild installation is showing up with a caution icon and noted as Unsubscribed
Incredibuild Agent - Unsubscribed
What does this mean exactly?
Some local IT started to help me get this software setup, but I've never had it running and it fell on the backburner. We updated our Network coordinator and my PC passed the test in connecting to the coordinator computer. What does one have to do to subscribe and what exactly would my PC be subscribing to?
You need someone with access to the coordinator to subscribe you. It's not something you can fix on the client end.
Read here.
Once configured the system tray icon on the client end will change to...
Incredibuild Agent - Enabled
Related
So I came across a strange issue: as soon as I hit send Web Push notification in One Signal dashboard, the Mysql server dies - memory usage goes to 100% and the cpu goes nuts. Soon after it crashes and Mysql resumes normal operation.
I must mention that this happens even if images used in the notification are not hosted on the same server. Even if nobody actually clicks the notifications for the first 5minutes, it still crashes.
Our list has about 11.000 subscribers.
What could be the issue? I just dont know what to try anymore. Tried upping the max_connections and other my.cnf settings according to mysqltuner.pl. No luck.
This is happening on a Magento 1.9 store, with the following specs: 24gb RAM, 240gb SSD, 12-core 2ghz, CentOS7, running Apache with REDIS, php5.5.
UPDATE: Fixed by revising the OneSignal settings and the way notifications are sent + enabled skip-name-resolve in my.cnf.
I have alerted this issue to onesignal several times but each time they suggest to go for good hosting service.
I think the problem is with the onesignal wp plugin. I have a dedicated cloud server from vultr but still site goes down right after new push notification.
You will have no problem if you send push notification directly from onesignal dashboard.
Because all my request goes to deaf ears, now I do not use onesignal.
I have Windows 10 build 1511, where I have installed SQL Server 2014.
After installation everything is OK.
I've made several times shutdown on Windows 10, and after if I turn on my PC everything is OK.
But if I restart the system, after the restart, the SQL Server service remains stopped (startup type is Automatic). I try another restart and shutdown, but the service doesn't start automatically anymore.
I've started the service manually, and after the service is started and everything works ok. If I shut down everything, it is ok afterwards. But if I just restart, the problem that I've described above appears again.
What can I do ?
Thank you !
Update
It seems that the problem is already reported to Microsoft :
https://connect.microsoft.com/SQLServer/feedback/details/1873617/sql-server-not-coming-online-after-os-upgrade-to-windows-10-even-when-startup-type-is-automatic
If you starts services.msc and serach for the SqlServer service, in properties, set the startup as automatic delay instead of automatic.
I'm dealing with the same issue on Win 2012. and it looks like the same issue described here:
Add your windows level user in following path:
Click on Start - Run - Secpol.msc Go to Local Policies - User right assignments
Act as a part of the Operating system
bypass Traverse checking
Lock pages in memory
Log on as a service
Log on a batch job
Replace process level token
If not, please add them and try restarting your system. Your SQL Server should be starting as a service. All the best.
I had this issue on Windows 10 and SQL Server 2014 Express.
The delayed start option didn't work for me, but here's what did work - granting higher DCOM permissions to the Network Service and Local Service accounts.
Click Start, type Component and then click the Component Services
app
In Component Services, double-click Component Services, and then double- click Computers. Right-click My Computer, and then click Properties.
Click the COM Security tab.
In the Launch and Activation Permissions area, click Edit Default.
Click Add, type Network Service, and then click OK. While Network Service is selected, click to select the Allow check boxes for the following items:
Local Launch
Remote Launch
Local Activation
Remote Activation
Repeat step 4 for the Local Service account.
Reboot and SQL Server should not start automatically.
In my case, this is a development environment so I'm less concerned about the security implications of this change and more concerned about getting it to work. So be advised to check out potential security ramifications if that's important in your situation.
pay Attention in suffix too
example: if in your user Secedit.msc is as contoso\usersql, in the windows service needs to be the same, I was putting usersql#contoso.com and was having problems to start the service automatic, after change to contoso\usersql, working fine
follow the way,
SQL SERVER INSTALLATION CENTER (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2019\Configuration Tools) > Maintenance > Edition Upgrade
and restart service
Another solution worked for me:
Open SQL Server Configuration Manager
Select SQL Server Services
Select any service (double click or right click and properties)
Go to "Log On" tab (My Log On settings was "This Account")
Choose "Built-in account" and "Local Service" under it.
Then I did this steps for every other services and it worked. I have no more problem while I am connecting to SQL Server Databases.
SQL Server Services Log On Settings
I faced this issue today , as my server is dependent on SQL server connection , that was also not booting up. It was simple in my case. I saw in services screen its status is STOP. So I started there ans it started working.
windows+R--> services.msc--> right click on the service and start it.
In my wp8 app,
I enter a open wifi which is operated by communication operator
blocked by a portal page that needs using account and password to log in
after I post some data to a https url
I have the ability to use the wifi network to access to internet freely.
Now,I encounter a problem:
before the https connection established successfully,it will be running the Online Certificate Status Protocol (OCSP)
OCSP needs to access to CA like veriSign to verify the server certificate status
but I have no internet access at this moment.
So,my app return a Webexception whose description is "The remote server returned an error: NotFound".I think it is because of the failure of OCSP.
Based on above,I want to find a solution to sovle this:
My point is to disable the OCSP mechanism，Do you know how to do this?
And I also would like to know if there is another solution to sovle the problem.
Hope your advice,Thanks!
The way you'd do that on .NET is to set the ServicePointManager.ServerCertificateValidationCallback delegate and perform the logic you want to perform. But, unfortunately that is not yet available on Windows Phone.
There are various uservoice suggestions related to this, for example:
http://windowsphone.uservoice.com/forums/101801-feature-suggestions/suggestions/2146033-allow-self-signed-and-corporate-certificates-for-s
http://windowsphone.uservoice.com/forums/101801-feature-suggestions/suggestions/4299617-client-ssl-certificate-authentication
They don't apply to you directly, but if they end up gaining access to ServicePointManager then you'll be able to do what you want to do.
How does one keep OpenShift gears up-to-date? For example, updates to:
The Linux kernel
Important components/libraries like libc
Apache
Apache modules like mod_wsgi
Python
Python packages
Does OpenShift automatically update these and then restart the gear (or reboot the node)? Or does OpenShift send email notifications and the end-user can restart the gear during maintenance windows? What is the model?
What got me thinking about this was back in January there was a remote-code-execution bug in Ruby on Rails that everyone had to patch immediately.
This FAQ seems to suggest that some level of upgrades happen automatically, but it isn’t clear whether this only applies to the OpenShift-specific code, or also other components like the kernel, Apache, etc.
I can tell you from my experience that changes to the openshift system are not always automatic. They had a change about 10 days ago and I'm still tracking down what they did to make my app run correctly. As far as I know there was no email sent. I did find a blog post of some of the major changes, not all. Of course, they introduced at least one bug that I know of. YMMV
My experiences over the last few weeks have been the following:
Last week there seemed to be an unannounced reboot of the server. I detected this by logging from a custom action hook. I didn't receive any email about it and I didn't see any notice at https://twitter.com/openshift_ops or https://openshift.redhat.com/app/status.
This week, there was the Heartbleed OpenSSL vulnerability and it seems like some gears were restarted. I didn't receive any email about it, Twitter didn't show anything, but there was information on the status page.
We have an active directory domain (let's call it foodomain) and a domain user account (foodomain\fooAppPoolUser) used for the IIS application pool identity.
We want to run the app pool under this user account and not under Network Service or the new AppPoolIdentity as we have to access SQL server and have multiple applications on IIS (with own app pools) accessing different databases.
The problem is that I can't find a clear HOW-TO explaining, which user rights have to be set for this user account and how IIS has to be setup so that this will work.
First I got errors (unfortunately I can't remember which ones), then I added fooAppPoolUser to the local admin group (Administrators, I know, was only to test), then it worked. Now I removed the user again, restarted IIS and it still works.
So I'm confused a bit and would like to know, how the configuration/setup has to be to have it working.
Somwhere I read, that the account needs to have the "Impersonate a client after authentication" user right. That's the reason I added the account to the Admin group (the user rights assignment is blocked via group policy, but this can for sure be changed if really needed.
I hope I was clear enough what the question is and hope somebody has an answer.
It's frustrating that this information is so hard to find, since some security admins seem to enjoy the cruel and unusual punishment of changing default policy settings to thwart installing apps within IIS.
Here's what I believe you should do to enable an account to work as an ApplicationPool identity:
Run aspnet_regiis -ga DOMAIN\USER to add permissions to access the IIS Metabase. (Exactly what that means, who knows?) aspnet_regiis reference
Add the user to the IIS_IUSRS group. This may be done automatically depending on the IIS configuration setting processmodel.manualGroupMembership but easiest to add it yourself.
If security policy is using windows defaults that's about it. If the security policy is locked down you may need to enable specific user rights for the account. The ones you have by default for ApplicationPoolIdentities (which seems a good place to start but not necessarily all required):
Access this computer from the network
Adjust memory quotas for a process
Allow log on locally
Bypass traverse checking
Generate security audit details
Impersonate a client after authentication - (Often not available by default on locked-down environments)
Log on as a batch job - (Often not available by default on locked-down environments)
Log on as a service - (I'm not sure this is needed)
Replace a process level token
If you're using windows auth and Kerberos (provider=Negotiate) then depending on the URL and if kernel-mode auth is on you might need to set up an SPN. I suggest switching to NTLM if possible. Otherwise, see articles below about SPNs and find a friendly domain admin to add them for you.
Fun reading:
Default permissions and user rights for IIS 7.0, 7.5, 8.0. This is the best reference, see the user rights at the bottom.
User Rights (on Windows Server 2008, but still interesting and helpful as it's a long article you can CTRL+F to find IIS-related comments)
User Rights Assignment on Server 2008 R2+. You have to drill into each right to see what it mentions about IIS.
How To: Create a Service Account for an ASP.NET 2.0 Application - pity there's no more recent version of this article.
SPN Checklist for Kerberos on IIS7/7.5
How to use SPNs - applies to IIS6 or to 7/8 if Kernel-mode authentication is turned off.
The reason why you application worked AFTER removing Administrator rights is that your application was compiled to the Framework temp folder using the administrator rights - Your application worked after removing the administrator rights because the application was compiled. If you update your application and it requires recompilation, the app pool account will need trusts again.
First I got errors (unfortunately I can't remember which ones), then
I added fooAppPoolUser to the local admin group (Administrators, I
know, was only to test), then it worked. Now I removed the user again,
restarted IIS and it still works.
I found the following link answered a similar question I had: http://www.iis.net/learn/manage/configuring-security/application-pool-identities
Basically, ApplicationPoolIdentity is a virtual user account that still behaves like NETWORK SERVICE, but without some of the down-sides; each app pool has it's very own ApplicationPoolIdenity account created with it.
More detailed information can also be found that is also specific to IIS 7.5 Application Pool Identities.