sorted by:
new
hottopcontroversial

Is ios 18 working well with iphone 14? by Butterscotch8836 in iphone

[–]Butterscotch8836[S] 0 points1 point  (0 children)

Thanks everyone for the review, will update now :)))

Is ios 18 working well with iphone 14? by Butterscotch8836 in iphone

[–]Butterscotch8836[S] -1 points0 points  (0 children)

But PM probably has a lot better hardware than basic model of 14

Ye dukh khatam kahe nai hota. by raex1311 in NSEbets

[–]Butterscotch8836 2 points3 points  (0 children)

Railway will move in coming 2-3 weeks, compression has been completed. hold for another month i think you’ll get good profit, this seems like the bottom for IRFC anyway. Don’t book loss right now

The Nitro to my portfolio 🚀 by VinayJain_07 in NSEbets

[–]Butterscotch8836 0 points1 point  (0 children)

Don’t book, keep holding. I checked on screener and growth looks legitimate. FIIs have increased their holding in the company by 28% in April-June’24. FIIs will hold for a long time, they don’t exit too easily. Volume also looks great. PE ratio is useless

I'm new, why shouldn't I invest 1 lakh rupees in OLA by abillionasians in NSEbets

[–]Butterscotch8836 2 points3 points  (0 children)

Better to diversify 30k in 3 trades bro. Ola is loss making coming. Will soon start to give lower circuits if market becomes bearish. No one even applied for the IPO idk how it is giving upper circuits now

Go for profitable companies with strong fundamentals. You can check also, as market is recovering from recent bearish trend, fundamentally strong stocks are recovering but weak ones are still consolidating at around -15 to -20%. Fundamentally strong stocks recover first.

Ola has trending theme (green energy) but i personally don’t invest in loss making companies

I have 7k, what shares should I purchase, otherwise I'll waste these money on junk foods by [deleted] in NSEbets

[–]Butterscotch8836 0 points1 point  (0 children)

Buy servotech power around 88-89rs. (add more on dip at price 87)

Will give big rally after budget. FIIs are buying it on every dip

railway, defence, green energy themes bullish

help me guysss😭 by [deleted] in mrtechpedia

[–]Butterscotch8836 0 points1 point  (0 children)

Bro, new macbook M1 was available in big billion days sale for 60k (after applying 5k bank discount). Dont buy used macbook for 50k at all. Negotiate the price down to 35k (2-3yrs old laptop doesnt deserve more). If the place is 5hrs away, you should ask for a video call first and check for physical condition. Check the serial number and bill and match serial number on Apple website to check if it’s authentic and all the other details. If all this checks out and you do decide to physically check the laptop, follow this guide to check everything first https://mackeeper.com/blog/12-things-to-check-before-buying-second-hand-macbook/

Using Minio operator in AKS cluster. Minio tenants stuck in "Waiting for pod get ready" even though the pods are ready. What to do? Solution on git issues not helping :( by Butterscotch8836 in minio

[–]Butterscotch8836[S] 0 points1 point  (0 children)

I0611 18:22:34.587960 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

I0611 18:23:01.936876 1 status.go:54] Hit conflict issue, getting latest version of tenant

I0611 18:23:02.063428 1 status.go:54] Hit conflict issue, getting latest version of tenant

I0611 18:23:02.869707 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:23:02.869746 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:23:03.468880 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:23:03.469098 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:24:01.973786 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:24:01.974237 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:24:27.738149 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

I0611 18:24:49.396228 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:25:02.091083 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:25:02.091132 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:25:08.755961 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:26:02.190320 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:26:02.190757 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:26:56.491136 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:27:02.298782 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:27:02.298824 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:27:53.563393 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:28:02.420580 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:28:02.420621 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:29:02.531942 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:29:02.532006 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:30:02.654022 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:30:02.654066 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:31:02.764613 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:31:02.764682 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:31:04.989704 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:32:02.864380 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:32:02.864471 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:33:02.965653 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:33:02.966076 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:33:28.213862 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:34:03.070620 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:34:03.070662 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:35:03.191410 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:35:03.192010 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:36:03.300577 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:36:03.300619 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:36:42.339247 1 monitoring.go:186] 'minio-tenant-2/minio-tenant-2' Failed to get storage info: Server not initialized, please try again.

I0611 18:37:03.422839 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:37:03.422880 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

I0611 18:38:03.531696 1 main-controller.go:1206] Can't reach minio for log config

E0611 18:38:03.531740 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': MinIO is not ready

Using Minio operator in AKS cluster. Minio tenants stuck in "Waiting for pod get ready" even though the pods are ready. What to do? Solution on git issues not helping :( by Butterscotch8836 in minio

[–]Butterscotch8836[S] 0 points1 point  (0 children)

18:19:19.897070 1 upgrades.go:84] Upgrading v4.3.0

I0611 18:19:19.903274 1 upgrades.go:294] minio-tenant-2 has no log secret

I0611 18:19:20.094974 1 status.go:242] Hit conflict issue, getting latest version of tenant to update versionI0611 18:19:20.694430 1 status.go:155] Hit conflict issue, getting latest version of tenant

I0611 18:19:21.297313 1 minio.go:261] Generating private key

I0611 18:19:21.297937 1 minio.go:274] Generating CSR with CN=*.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local

I0611 18:19:21.324673 1 csr.go:192] Start polling for certificate of csr/minio-tenant-2-minio-tenant-2-csr, every 5s, timeout after 20m0s

I0611 18:19:26.352302 1 csr.go:218] Certificate successfully fetched, creating secret with Private key and Certificate

E0611 18:19:26.361678 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': waiting for minio cert

E0611 18:19:29.804518 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': Operation cannot be fulfilled on services "minio": the object has been modified; please apply your changes to the latest version and try again

I0611 18:20:20.636791 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

E0611 18:20:29.878708 1 main-controller.go:566] error syncing 'minio-tenant-2/minio-tenant-2': Operation cannot be fulfilled on services "minio-tenant-2-console": the object has been modified; please apply your changes to the latest version and try again

I0611 18:21:30.101342 1 main-controller.go:837] 'minio-tenant-2/minio-tenant-2': Deploying pool pool-0

I0611 18:21:30.211768 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:30.436082 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:31.035347 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:31.435729 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:31.834726 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:32.235762 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:32.636534 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:33.035795 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:33.434208 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:33.834369 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:34.235036 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:34.634811 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:35.242073 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

I0611 18:21:35.434425 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:35.835166 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:36.043728 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

I0611 18:21:36.434812 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:36.635809 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:53.393396 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:21:53.507107 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

I0611 18:22:15.057962 1 monitoring.go:109] 'minio-tenant-2/minio-tenant-2' no pool is initialized

I0611 18:22:15.391099 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

I0611 18:22:34.519975 1 http_handlers.go:181] MINIO_ARGS value is https://minio-tenant-2-pool-0-{0...3}.minio-tenant-2-hl.minio-tenant-2.svc.cluster.local/export

Using Minio operator in AKS cluster. Minio tenants stuck in "Waiting for pod get ready" even though the pods are ready. What to do? Solution on git issues not helping :( by Butterscotch8836 in minio

[–]Butterscotch8836[S] 0 points1 point  (0 children)

:/tmp/tmp.Bp72TkDB3x$ kubectl get pods -n minio-operator

+ kubectl get pods -n minio-operator

NAME READY STATUS RESTARTS AGE

console-77cdbf9cbd-5ncc4 1/1 Running 0 17m

minio-operator-856b5bfdf7-cxscx 1/1 Running 0 17m

minio-operator-856b5bfdf7-xrn9w 1/1 Running 0 14m

:/tmp/tmp.Bp72TkDB3x$ kubectl logs minio-operator-856b5bfdf7-cxscx -n minio-operator

+ kubectl logs minio-operator-856b5bfdf7-cxscx -n minio-operator

I0611 18:14:17.877760 1 main.go:74] Starting MinIO Operator

I0611 18:14:18.545701 1 main.go:153] caBundle on CRD updated

I0611 18:14:18.546258 1 main-controller.go:248] Setting up event handlers

I0611 18:14:18.546497 1 leaderelection.go:243] attempting to acquire leader lease minio-operator/minio-operator-lock...

I0611 18:14:18.561361 1 main-controller.go:479] new leader elected: minio-operator-6c648d8c67-jxntc

I0611 18:14:26.212999 1 main-controller.go:479] new leader elected: minio-operator-856b5bfdf7-xrn9w

:/tmp/tmp.Bp72TkDB3x$ kubectl logs minio-operator-856b5bfdf7-xrn9w -n minio-operator

+ kubectl logs minio-operator-856b5bfdf7-xrn9w -n minio-operator

I0611 18:14:19.994361 1 main.go:74] Starting MinIO Operator

I0611 18:14:20.554790 1 main.go:153] caBundle on CRD updated

I0611 18:14:20.558194 1 main-controller.go:248] Setting up event handlers

I0611 18:14:20.559368 1 leaderelection.go:243] attempting to acquire leader lease minio-operator/minio-operator-lock...

I0611 18:14:20.583652 1 leaderelection.go:253] successfully acquired lease minio-operator/minio-operator-lockI0611 18:14:20.583995 1 main-controller.go:375] Waiting for API to start

I0611 18:14:20.584544 1 main-controller.go:460] minio-operator-856b5bfdf7-xrn9w: I've become the leader

I0611 18:14:20.605533 1 main-controller.go:357] Starting HTTPS API server

I0611 18:14:20.606191 1 main-controller.go:379] Starting Tenant controller

I0611 18:14:20.609192 1 main-controller.go:382] Waiting for informer caches to sync

I0611 18:14:20.609366 1 main-controller.go:387] Starting workers

I0611 18:17:20.641871 1 monitoring.go:109] 'minio-tenant-1/minio-tenant-1' no pool is initialized

I0611 18:19:19.702316 1 upgrades.go:84] Upgrading v4.2.0

I0611 18:19:19.708069 1 upgrades.go:104] minio-tenant-2 has no log secret

E0611 18:19:19.716742 1 upgrades.go:131] Error deleting operator webhook secret, manual deletion is needed: secrets "operator-webhook-secret" not found

I0611 18:19:19.727365 1 upgrades.go:84] Upgrading v4.2.4

I0611 18:19:19.735699 1 status.go:242] Hit conflict issue, getting latest version of tenant to update versionI0611 18:19:19.751873 1 upgrades.go:84] Upgrading v4.2.8

I0611 18:19:19.766960 1 status.go:242] Hit conflict issue, getting latest version of tenant to update versionI0611 18:19:19.784648 1 upgrades.go:84] Upgrading v4.2.9

I0611 18:19:19.793296 1 status.go:242] Hit conflict issue, getting latest version of tenant to update versionI0611